[EMAIL PROTECTED] said:
> *sigh* this isn't just powerpc. this is x86 too. I can't get ANY
> kernels
> to compile with gcc 2.95 or 2.91. Folks, I think at this point it's
> SERIOUSLY advisable to just abandon gcc 2.9x as primary and change it
> to
> optional. There's just too much stuff that will
On Tue, Nov 30, 1999 at 04:38:06AM -0500, Justin McKillican wrote:
> _any_ kernels? i just compiled 2.2.13 on gccf 2.95.1 and 2.95.2.
I haven't had problems on x86, but I have had very few kernels work on
the ppc box.
Ciao,
--
David N. Welton -+- [EMAIL PROTECTED] -+- http://www.efn.org/~da
On Tue, Nov 30, 1999 at 09:54:23AM +0100, VALETTE Eric wrote:
> NB : be sure you use -fno-strict-aliasing when compiling as linux is known
> to be broken using the strict-aliasin option.
And so, in 2.95.2 and higher, they've made -fno-strict-aliasing the
default again.
Dan
/-
On Tue, Nov 30, 1999 at 02:37:28AM -0500, Phillip R. Jaenke wrote:
> David Welton wrote:
> >
> > So, I was talking with Cort regarding my ongoing RS6K troubles, and he
> > mentioned that trying an older compiler might help.
> >
> > I did indeed have a better time of getting a v2.2.14-preX going w
Previously David Welton wrote:
> How do I track down what is causing that?
There are patches to continously print some registers such as the
instructionpointer on your display; that allows you to see exactly
where your kernel has crashed.
I'm not sure if they're available for powerpc as well thou
> *sigh* this isn't just powerpc. this is x86 too. I can't get ANY kernels
> to compile with gcc 2.95 or 2.91. Folks, I think at this point it's
> SERIOUSLY advisable to just abandon gcc 2.9x as primary and change it to
> optional. There's just too much stuff that will NOT compile with it. I
> mea
> "David" == David Welton <[EMAIL PROTECTED]> writes:
David> How do I track down what is causing that?
First try to find the .c file that is causing the problem. This may be
easy or not :(. Then check that compiling that file only with egcs-1.1.2
fixes the problem. Then split the file in mult
On Tue, Nov 30, 1999 at 09:32:39AM +0100, VALETTE Eric wrote:
> There were two serious bugs in gcc-2.95.1 for PPC. I found them
> while working on RTEMS on MCP750 (PowerPC Compaq PCI borad where I
> also ported linux). I reported them and they are now fixed in
> gcc-2.95.2. One was fixed within a
> "Brendan" == Brendan Simon <[EMAIL PROTECTED]> writes:
Brendan> "Phillip R. Jaenke" wrote:
Phillip> *sigh* this isn't just powerpc. this is x86 too. I can't get ANY
kernels
Phillip> to compile with gcc 2.95 or 2.91. Folks, I think at this point it's
Phillip> SERIOUSLY advisable to just aba
"Phillip R. Jaenke" wrote:
> *sigh* this isn't just powerpc. this is x86 too. I can't get ANY kernels
> to compile with gcc 2.95 or 2.91. Folks, I think at this point it's
> SERIOUSLY advisable to just abandon gcc 2.9x as primary and change it to
> optional. There's just too much stuff that will N
David Welton wrote:
>
> So, I was talking with Cort regarding my ongoing RS6K troubles, and he
> mentioned that trying an older compiler might help.
>
> I did indeed have a better time of getting a v2.2.14-preX going with
> the 2.91 on my yellow dog partition.
>
> If we don't have a compiler tha
So, I was talking with Cort regarding my ongoing RS6K troubles, and he
mentioned that trying an older compiler might help.
I did indeed have a better time of getting a v2.2.14-preX going with
the 2.91 on my yellow dog partition.
If we don't have a compiler that can generate good code for kernels,
12 matches
Mail list logo
