dropbear glibc 2.1.3 compile error

Miles Roper mroper at westcoastdhb.org.nz
Mon Jan 31 12:43:05 WST 2005


ok, didn't work,

added this down the bottom of includes.h

typedef __ss_family ss_family;

got the below errors.  probably something simple, I'm not really that
conversant with C, so please be gentle ;o)

In file included from debug.h:28,
                 from includes.h:30,
                 from dbutil.c:51:
includes.h:141: parse error before `ss_family'
includes.h:141: warning: data definition has no type or storage class
In file included from compat.h:28,
                 from includes.h:116,
                 from dbutil.c:51:
includes.h:141: parse error before `ss_family'
includes.h:141: warning: data definition has no type or storage class
In file included from fake-rfc2553.h:45,
                 from includes.h:117,
                 from dbutil.c:51:
includes.h:141: parse error before `ss_family'
includes.h:141: warning: data definition has no type or storage class
In file included from dbutil.c:51:
includes.h:141: parse error before `ss_family'
includes.h:141: warning: data definition has no type or storage class
In file included from dbutil.h:29,
                 from dbutil.c:52:
includes.h:141: parse error before `ss_family'
includes.h:141: warning: data definition has no type or storage class
In file included from buffer.h:29,
                 from dbutil.h:30,
                 from dbutil.c:52:
includes.h:141: parse error before `ss_family'
includes.h:141: warning: data definition has no type or storage class
In file included from session.h:28,
                 from dbutil.c:54:
includes.h:141: parse error before `ss_family'
includes.h:141: warning: data definition has no type or storage class
In file included from dss.h:28,
                 from signkey.h:29,
                 from session.h:31,
                 from dbutil.c:54:
includes.h:141: parse error before `ss_family'
includes.h:141: warning: data definition has no type or storage class
In file included from rsa.h:28,
                 from signkey.h:30,
                 from session.h:31,
                 from dbutil.c:54:
includes.h:141: parse error before `ss_family'
includes.h:141: warning: data definition has no type or storage class
In file included from kex.h:28,
                 from session.h:32,
                 from dbutil.c:54:
includes.h:141: parse error before `ss_family'
includes.h:141: warning: data definition has no type or storage class
In file included from algo.h:29,
                 from kex.h:29,
                 from session.h:32,
                 from dbutil.c:54:
includes.h:141: parse error before `ss_family'
includes.h:141: warning: data definition has no type or storage class
In file included from auth.h:28,
                 from session.h:33,
                 from dbutil.c:54:
includes.h:141: parse error before `ss_family'
includes.h:141: warning: data definition has no type or storage class
In file included from channel.h:28,
                 from session.h:34,
                 from dbutil.c:54:
includes.h:141: parse error before `ss_family'
includes.h:141: warning: data definition has no type or storage class
In file included from packet.h:29,
                 from session.h:37,
                 from dbutil.c:54:
includes.h:141: parse error before `ss_family'
includes.h:141: warning: data definition has no type or storage class
In file included from loginrec.h:32,
                 from chansession.h:28,
                 from session.h:39,
                 from dbutil.c:54:
includes.h:141: parse error before `ss_family'
includes.h:141: warning: data definition has no type or storage class
In file included from atomicio.h:31,
                 from dbutil.c:55:
includes.h:141: parse error before `ss_family'
includes.h:141: warning: data definition has no type or storage class
dbutil.c: In function `getaddrstring':
dbutil.c:362: structure has no member named `ss_family'
dbutil.c:366: structure has no member named `ss_family'
dbutil.c: In function `getaddrhostname':
dbutil.c:404: structure has no member named `ss_family'
dbutil.c:408: structure has no member named `ss_family'
gcc: file path prefix `//lib' never used
make: *** [dbutil.o] Error 1 

-----Original Message-----
From: Matt Johnston [mailto:matt at ucc.asn.au] 
Sent: Monday, 31 January 2005 02:21 a.m.
To: Miles Roper
Cc: 'dropbear at ucc.asn.au'; Thinstation-Developer
(thinstation-developer at lists.sourceforge.net)
Subject: Re: dropbear glibc 2.1.3 compile error

On Fri, Jan 28, 2005 at 09:48:05PM +1300, Miles Roper wrote:
> 
> Hi,
> 
> I get the below errors when compiling with gcc 2.95.3 and glibc 2.1.3.
> 
> gcc -I. -I./libtomcrypt -B//lib -Wl,-rpath-link,//lib -Os -mcpu=i586
> -march=i386 -DDROPBEAR_SERVER -DDROPBEAR_CLIENT   -c -o dbutil.o dbutil.c
> dbutil.c: In function `getaddrstring':
> dbutil.c:362: structure has no member named `ss_family'
> dbutil.c:366: structure has no member named `ss_family'
> dbutil.c: In function `getaddrhostname':
> dbutil.c:404: structure has no member named `ss_family'
> dbutil.c:408: structure has no member named `ss_family'
> gcc: file path prefix `//lib' never used
> make: *** [dbutil.o] Error 1
> 
> I done a seach using google and found a similar problem.  Can we get 
> this fixed in dropbear?

I'll take a look at getting a fix in for the next release.

I guess for the moment a "typedef __ss_family ss_family"
would be a hacky workaround in includes.h?

Alternatively, if you're just targetting ipv4 on linux, removing the whole
if/else block mentioning ss_family should be safe AFAIK.

Matt

> 
> Thanks
> 
> Miles
> 
> 
> | ftpd.c:1093: structure has no member named `ss_family'
> 
> This message is because the Linux sockaddr_storage struct member is 
> called __ss_family not ss_family, if using configure add "#define
HAVE__SS_FAMILY"
> to the generated src/config.h (before the Socket macros), then run make.
> You could also try using build, edit config.h.noac, change "#undef INET6"
> to "#define INET6" followed by ./build lnx should work.
> 
> ==================================================
> Attention:
> The information contained in this message and/or attachments is 
> intended only for the person or entity to which it is addressed and 
> may contain confidential and/or privileged material.  Any review, 
> retransmission, dissemination or other use of, or taking of any action 
> in reliance upon, this information by person or entities other than 
> the intended recipient is prohibited.  If you receive this in error,
please contact the sender and delete the material from your system and
destroy any copies.
> ===================================================

==================================================
Attention:
The information contained in this message and/or attachments is intended
only for the person or entity to which it is addressed and may contain
confidential and/or privileged material.  Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon,
this information by person or entities other than the intended recipient
is prohibited.  If you receive this in error, please contact the sender and delete the material from your system and destroy any copies.
===================================================



More information about the Dropbear mailing list