Glibc 2.3.2 and gcc 3.3

[Jasper Huijsmans]

I'll just continue this thread with more gcc 3.3 stuff.

I can't build linux 2.4.20, but I can build 2.4.21-rc2 with one
adjustment:

in net/core/rtnetlink.c, line 397, there is a function definition for 

====

extern __inline__ int rtnetlink_rcv_skb(struct sk_buff *skb)
{
...

====

I had to change it to make the linker find it:

====

extern __inline__ int rtnetlink_rcv_skb(struct sk_buff *skb);

__inline__ int rtnetlink_rcv_skb(struct sk_buff *skb)
{
...

====

	Jasper


On Thu, 15 May 2003 02:05:41 +0200
Niki Guldbrand <nikig at vip.cybercity.dk> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi all.
> 
> The issue with glibc 2.3.2 not want ot be compilled by gcc 3.3 has
> been fix and the fix has been added to the moonbase...
> 
> It's a simple little patch... (Only one function needs to be fixed..)
> This issue has been fix in glibc cvs repository the 3rd of may.
> 
> The function format has been changed for the new gcc
> 
> int name( arg1, arg2 )
>   int arg1;
>   int arg2;
> {
>   blah;
>   blah;
> }
> 
> Is not allowed any more, and there for this format has to be used
> instead
> 
> int name ( int arg1, int arg2 )
> {
>   blah;
>   blah;
> }
> 
> I hope you get the idea ;o)
> 
> 
> Happy hacking ppl...
> 
> Niki Guldbrand
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.2 (GNU/Linux)
> 
> iD8DBQE+wtnVljJ8M8hBdegRApXnAKCEp1eJMEf/vH5AVGcvForwUAlGAQCfSwKY
> HmGZRWKaC57K6+O9geGE+vM=
> =hmf2
> -----END PGP SIGNATURE-----
> _______________________________________________
> Lunar-dev mailing list
> Lunar-dev at lunar-linux.org
> http://lunar-linux.org/mailman/listinfo/lunar-dev