[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-ppc
Subject:    Re: compiling issues
From:       tarag <tarag () cybercable ! fr>
Date:       1999-04-09 9:09:39
[Download RAW message or body]


yes, it finally worked fine after patching the kernel headers

thanks to all

>
>Yo! Gary (& all)! this is the classic glibc-1.99 header bug :-)
>
>You wrote the patch that fixed, probably haven't seen it in a while on your
>box. Get the glibc_199 patch from ftp.linuxppc.org/linuxppc/users/gdt/ in
>the kernel-patches area.
>
>--
>+--------------------------------------------------------------------+
>|            .-'''''-.       Kevin Puetz                             |
>|          .'   _/|   `.                                             |
>|         :   =/_/      :    kp11901@cedarnet.org -preferred         |
>|        :   _/ |        :   Kevin.Puetz@039-server.pls.uni.edu      |
>|       (\  /  ,|        :   webmaster@039-server.pls.uni.edu        |
>|        \\/^\/||__     :                                            |
>|     _/~`~`""~`"` \_ .'  "Could you please continue the petty       |
>|  __/  -'/  `-._ `\_\__   bickering?  I find it - most intriguing." |
>|/     /-'`  `\   \  \-.\    --Data, STTNG, "Haven"                  |
>+--------------------------------------------------------------------+
>
>----------
>>From: Gary Thomas <gdt@linuxppc.ORG>
>>To: tarag <tarag@cybercable.fr>
>>Cc: linuxppc-user@lists.linuxppc.ORG
>>Subject: RE: compiling issues
>>Date: Thu, Apr 8, 1999, 9:46 AM
>>
>
>>
>>
>> On 08-Apr-99 tarag wrote:
>>>
>>> Hello everyone,
>>>
>>> I'm running R4.1 on a G3 series with kernel 2.2.5, the latest egcs and
>>> binutils from Gary Thomas directory and i often encounter such errors
>>> when compiling:
>>>
>>>
>>> In file included from /usr/include/netinet/in.h:24,
>>>                  from file.c:81:
>>> /usr/include/sys/socket.h:146: warning: `struct msghdr' declared inside
>>> parameter list
>>> /usr/include/sys/socket.h:146: warning: its scope is only this definition
>>> or declaration,
>>> /usr/include/sys/socket.h:146: warning: which is probably not what you
>>> want.
>>> /usr/include/sys/socket.h:150: warning: `struct msghdr' declared inside
>>> parameter list
>>> In file included from /usr/include/netinet/in.h:27,
>>>                  from file.c:81:
>>> /usr/include/linux/in.h:110: parse error before `sa_family_t'
>>> /usr/include/linux/in.h:110: warning: no semicolon at end of struct or
>>> union
>>> /usr/include/linux/in.h:117: parse error before `}'
>>> make[1]: *** [file.o] Error 1
>>> make: *** [libfile/libfile.a] Error 2
>>>
>>> it is really anoying because it appears nearly with all programs that i
>>> try to compile
>>>
>>
>> These sort of things don't normally happen (you'll need to take my word
>> for it :-)
>>
>> There must be something special about your program, perhaps in the way
>> the include files are being specified.  The Linux includes are a little
>> finicky in this area, BTW.
>>
>> What is/are the source file?
>> Did you write this or import it from somewhere?
>>
>> If you want to send me the file/pointer, I'll be glad to give it a quick
>> look and help you solve this problem.
>>
>> ------------------------------------------------------------------------
>> Gary Thomas                              |
>> email: gdt@linuxppc.org                  | "Fine wine is a necessity of
>>    ... opinions expressed here are mine  |        life for me"
>>        and no one else would claim them! |
>>                                          |      Thomas Jefferson
>> ------------------------------------------------------------------------
>>
>>
>

[[ This message was sent via the linuxppc-user mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-user  if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

[prev in list] [next in list] [prev in thread] [next in thread]