> > If you are using pgcc, try getting a real less-buggy compiler, like egcs1.1.2
> > or gcc-2.95 (even 2.96 willl work).
>
> ... not always. I've had problems with gcc "2.96" from RH-7.0
> - the compiler was generating obviously incorrect code in some cases
> (and it wasn't .c code fault but a c
On 03.12 Krzysztof Halasa wrote:
> "J . A . Magallon" <[EMAIL PROTECTED]> writes:
>
> > If you are using pgcc, try getting a real less-buggy compiler, like
> egcs1.1.2
> > or gcc-2.95 (even 2.96 willl work).
>
> ... not always. I've had problems with gcc "2.96" from RH-7.0
> - the compiler was
"J . A . Magallon" <[EMAIL PROTECTED]> writes:
> If you are using pgcc, try getting a real less-buggy compiler, like egcs1.1.2
> or gcc-2.95 (even 2.96 willl work).
... not always. I've had problems with gcc "2.96" from RH-7.0
- the compiler was generating obviously incorrect code in some cases
Thanks for the tips. Yes, I'm using pgcc... Guess I'll switch back to gcc.
Thanks again
tw
Le jour Sun Mar 11, 2001 at 08:54:08PM -0600, Tim Whitehead a ecrit...
> On a compile of 2.4.2 I get the following (using make bzImage)
>
>
> make[2]: Leaving directory `/usr/src/linux-2.4.2/linux/
On 03.12 [EMAIL PROTECTED] wrote:
> On a compile of 2.4.2 I get the following (using make bzImage)
> init/main.o: In function `check_fpu':
> init/main.o(.text.init+0x63): undefined reference to `__buggy_fxsr_alignment'
> make: *** [vmlinux] Error 1
If you are using pgcc, try getting a real less
5 matches
Mail list logo