From: Roland Dreier <roland@topspin.com>
To: "hyding" <nari_dhy@nari-china.com>
Cc: "linuxppc-embed" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: gcc-3.3.1-glibc-2.3.2-binutils-2.14 cross compile kernel problems
Date: 02 Dec 2003 08:18:05 -0800 [thread overview]
Message-ID: <52k75f8a82.fsf@topspin.com> (raw)
In-Reply-To: <001001c3b8a4$f8beff80$4844900a@hydingnb1>
hyding> hi, I have built cross-toolchain with gcc-3.3.1,
hyding> binutils-2.14, glibc-2.3.2 and linux-2.4.18 header files. I
hyding> have succeeded in compiling a test program with gcc into a
hyding> static app. This test program runs well in the target. But i
hyding> failed to build kernel with gcc. The info is as follow:
unistd.h does have precisely the right clobber lists for its syscall
macros. This patch from Ed Swarthout should help:
http://www.geocrawler.com/archives/3/3/2002/10/0/9962740/
- Roland
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-12-02 16:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 7:21 gcc-3.3.1-glibc-2.3.2-binutils-2.14 cross compile kernel problems hyding
2003-12-02 16:18 ` Roland Dreier [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=52k75f8a82.fsf@topspin.com \
--to=roland@topspin.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=nari_dhy@nari-china.com \
/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;
as well as URLs for NNTP newsgroup(s).