discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gcc 3.0 or bug ?


From: Dennis Leeuw
Subject: Re: gcc 3.0 or bug ?
Date: Fri, 04 May 2001 11:01:10 +0200

Richard Frith-Macdonald wrote:

> On Friday, May 4, 2001, at 08:13 AM, Dennis Leeuw wrote:
>
> > Hi all,
> >
> > While testing gcc 3.0 I took a CVS snapshot yesterday.
> > I build gcc 3.0 with objc, then build libxml and make, gnustep-objc,
> > make, ffcall, and now base, which gives an error.
> > I didn't build gmp, and ssl, so these are not available.
> >
> > Now the question is is this error related to gcc 3.0 or is it a bug in
> > the CVS snapshot I have ?
> >
> > Could someone explain to me how to solve this puzzle ?
> >
> > behavior.m: In function `behavior_class_add_class':
> > behavior.m:112: structure has no member named `methodLists'
> > behavior.m:121: structure has no member named `methodLists'
>
> Don't know ... but I get no such problem with gcc-3.1 (two days old from
> CVS)
> and GNUstep base (five minutes old from CVS)

gcc-3.1 ? I took a CVS snapshot at the same date from the 3.0 branch,
didn't know there was 3.1, hmmm

Okay I took a new snapshot from base and compiled with both gcc-3.0 and
gcc-2.95.2.
2.95.2 went fine, no problems at all and gcc-3.0 now gives me:

mframe.m: In function `mframe_decode_return':
mframe.m:1737: Internal compiler error in make_decl_rtl, at varasm.c:591
Please submit a full bug report, with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
make[3]: *** [shared_obj/ix86/linux-gnu/gnu-gnu-gnu/mframe.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[2]: *** [libgnustep-base.build] Error 2
make[1]: *** [libgnustep-base.all.library.variables] Error 2
make[1]: Leaving directory `/opt/src/core/base/Source'
make: *** [internal-all] Error 2

Is gcc-3.x more memory sensitive ?

I am lost. Guess I have to stick with 2.95.2 then.

Dennis

Attachment: dleeuw.vcf
Description: Card for Dennis Leeuw


reply via email to

[Prev in Thread] Current Thread [Next in Thread]