(usagi-users 03719) Re: is there a minimum gcc version requirement?

hi tim,

thanks for your time to reply.

may i ask what version gcc & glibc you were using at that time?

also, as you are the first response i have had, i wonder if you know?

is anyone using this code in a ppc cross compile environment?

thanks!  jackc...


Tim McFadden wrote:
> Dear Mr. Craig,
>
> When I did the earlier USAGI release, using SUSE Linux 10.0, I had to 
> change the source code to avoid compile errors.
> I couldn't find any gcc options that would fix them.
>
> The good news is that the apps appear to work and the new kernel boots.
>
> Tim McFadden
> -------------------------------------------
> Interniche Technologies Inc.
> 51 East Campbell Avenue, Suite 160
> Campbell, CA, 95008
> Ph:   408-540-1160x207
> Fax: 408-540-1161
> www.iniche.com
>
>
>
> jackc wrote:
>> hi folks,
>>
>> i am trying to build the 09042006 release. my RH has gcc 3.4.3.
>> with a minor tweak to a switch/case stmnt, i was able to buld the 
>> libraries.
>>
>> but, i am getting a compile error on building comsat, ...
>>
>> make[1]: Leaving directory `/home/jackc/ipv6/usagi/usagi/libnet-tools'
>> for subdir in comsat; do                \
>>        make -C $subdir;                \
>> done
>> make[1]: Entering directory `/home/jackc/ipv6/usagi/usagi/comsat'
>> gcc -I../libinet6/include -g -O2 -D_USAGI -DINET6     -c -o comsat.o 
>> comsat.c
>> In file included from /usr/include/sys/socket.h:35,
>>                 from comsat.c:47:
>> ../libinet6/include/bits/socket.h:265: error: syntax error before '{' 
>> token
>> ../libinet6/include/bits/socket.h:274: error: invalid type argument 
>> of `->'
>> ../libinet6/include/bits/socket.h:275: error: syntax error before "if"
>> make[1]: *** [comsat.o] Error 1
>> make[1]: Leaving directory `/home/jackc/ipv6/usagi/usagi/comsat'
>> make: *** [apps] Error 2
>>
>> any suggestions? thx...
>>
>
>
>
>

-- 
Jack Craig

Linux/XPath Team
Brocade Communications Systems, Inc.
1600 Technology Dr.
San Jose, CA  95110
408.333.7478
Direct E-mail:  [email protected]