Re: Still kernel compilation failures

1999-07-23 Thread Bruce Evans
>>-O works because optimisation removes an unused reference to a nonexistent >>variable. The variable once existed and was used. It still exists under >>a different name. > >So you're saying that both the compiler and the code are broken? Only the code. Bruce To Unsubscribe: send mail to [EM

Re: Still kernel compilation failures

1999-07-22 Thread Bob Bishop
At 14:24 23/07/99 +1000, Bruce Evans wrote: >>> > Put -O back in the COPTFLAGS. >>> >>> It works now. Is there any explaination why -O is required? :) >> >>Noone compiles without -O, so(/and) it's not supported. My take is > >It is supported, but someone broke it. > >>that EGCS says "Hey, I am in

Re: Still kernel compilation failures

1999-07-22 Thread Bruce Evans
>> It is supported, but someone broke it. > >Since when? Every so often someone comes along (from a pool of maybe 5 >people who _don't_ use -O) and complains about it being broken. If My last fix for a -O related bug was on 1999/05/13 for brooktree.c (memcmp() was used, but memcmp() doesn't exist

Re: Still kernel compilation failures

1999-07-22 Thread Brian F. Feldman
On Fri, 23 Jul 1999, Bruce Evans wrote: > >> > Put -O back in the COPTFLAGS. > >> > >> It works now. Is there any explaination why -O is required? :) > > > >Noone compiles without -O, so(/and) it's not supported. My take is > > It is supported, but someone broke it. Since when? Every so often

Re: Still kernel compilation failures

1999-07-22 Thread Bruce Evans
>> > Put -O back in the COPTFLAGS. >> >> It works now. Is there any explaination why -O is required? :) > >Noone compiles without -O, so(/and) it's not supported. My take is It is supported, but someone broke it. >that EGCS says "Hey, I am in optimization level foobar! I can optimize >for unuse

RE: Still kernel compilation failures

1999-07-22 Thread David Schwartz
> Noone compiles without -O, so(/and) it's not supported. My take is > that EGCS says "Hey, I am in optimization level foobar! I can optimize > for unused code. Hmm... that's unused, so...". Either that or its > debugging support is really uNFed up. Actually, more likely at high enough o

Re: Still kernel compilation failures

1999-07-22 Thread Brian F. Feldman
On Fri, 23 Jul 1999, Thomas Schuerger wrote: > > > ... > > > vfs_init.o: In function `vfs_register': > > > vfs_init.o(.text+0x8a1): undefined reference to `sysctl(void, float, short)' > > > *** Error code 1 > > > 1 error > > > Exit 2 > > > > > > > > > What am I doing wrong? Any help is greatly

Re: Still kernel compilation failures

1999-07-22 Thread Thomas Schuerger
> > ... > > vfs_init.o: In function `vfs_register': > > vfs_init.o(.text+0x8a1): undefined reference to `sysctl(void, float, short)' > > *** Error code 1 > > 1 error > > Exit 2 > > > > > > What am I doing wrong? Any help is greatly appreciated. > > > > Put -O back in the COPTFLAGS. It works n

Re: Still kernel compilation failures

1999-07-22 Thread Brian F. Feldman
On Thu, 22 Jul 1999, Thomas Schuerger wrote: > Hi! > > I updated the source tree, built and installed the world today > and tried to make a new kernel. Compilation stops when it > comes to linking: > > ... > vfs_init.o: In function `vfs_register': > vfs_init.o(.text+0x8a1): undefined reference