[lkml]   [2002]   [Apr]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Bug in compiling
On Wed, 3 Apr 2002, Keith Owens wrote:
> On Wed, 3 Apr 2002 00:57:06 -0800 (PST),
> Robin Johnson <> wrote:
> >While mass compiling a new kernel for my slew of systems, I had an unusual
> >problem
> >
> >gcc barfs and gives this huge error:
> >gcc -D__KERNEL__ -I/usr/src/linux-2.4.19-pre4-ac3/include -Wall
> >-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
> >-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
> >-march=i686 -DKBUILD_BASENAME=exec_domain -DEXPORT_SYMTAB -c
> >exec_domain.c
> >exec_domain.c:234: parse error before `register_exec_domain'
> >exec_domain.c:235: parse error before `unregister_exec_domain'
> >exec_domain.c:236: parse error before `__set_personality'
> >exec_domain.c:287: parse error before `abi_defhandler_coff'
> >...
> All EXPORT_SYMBOL. You would get that behaviour if gcc did not
> recognise EXPORT_SYMBOL as a macro. Probably random data corruption.
Of the pair of machines, I upgraded one of them to GCC 3.0.4, while
leaving the other at 2.95.3.

The identical source and config file compiles fine on the one, but not on
the other. It gives that exec_domain slew.c of errors.

So is this a GCC bug that I have located, or something more with the
kernel?, as Documentation/Changes lists GCC 2.95.3 at the minimal version

I would like to avoid the GCC3 tree as it stands presently, as I have some
C++ code that can not be ported at this time to work with GCC3, and only
works with GCC2.95.3.

Any ideas?

Thanks in advance.

(Again, please CC replies to me as I am not subscribed to the list.)

Robin Hugh Johnson
E-Mail :
Home Page :
ICQ# : 30269588 or 41961639

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:22    [W:0.062 / U:0.876 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site