From: Keith Owens <kaos@ocs.com.au>
To: Robin Johnson <robbat2@fermi.orbis-terrarum.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bug in compiling
Date: Thu, 04 Apr 2002 17:04:45 +1000 [thread overview]
Message-ID: <22591.1017903885@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Wed, 03 Apr 2002 21:34:59 PST." <Pine.LNX.4.43.0204032116410.25829-100000@fermi.orbis-terrarum.net>
On Wed, 3 Apr 2002 21:34:59 -0800 (PST),
Robin Johnson <robbat2@fermi.orbis-terrarum.net> wrote:
>On Wed, 3 Apr 2002, Keith Owens wrote:
>> On Wed, 3 Apr 2002 00:57:06 -0800 (PST),
>> Robin Johnson <robbat2@fermi.orbis-terrarum.net> wrote:
>> >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.
On the failing system,
cd /usr/src/linux-2.4.19-pre4-ac3/kernel
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 \
-E -c exec_domain.c -o exec_domain.i
and send exec_domain.i to kaos@ocs.com.au (not the list).
prev parent reply other threads:[~2002-04-04 7:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 8:57 Robin Johnson
2002-04-03 11:16 ` Keith Owens
2002-04-04 5:34 ` Robin Johnson
2002-04-04 7:04 ` Keith Owens [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=22591.1017903885@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=robbat2@fermi.orbis-terrarum.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®