From: "Rupert Wood" <me@rupey.net>
To: <hlin@hauppauge.com>
Cc: <gcc-help@gcc.gnu.org>
Subject: RE: build cross gcc for ppc-linux
Date: Thu, 18 Apr 2002 17:15:00 -0000 [thread overview]
Message-ID: <616BE6A276E3714788D2AC35C40CD18D120075@whale.softwire.co.uk> (raw)
In-Reply-To: <616BE6A276E3714788D2AC35C40CD18D5B2A8F@whale.softwire.co.uk>
Harry Lin wrote:
> On host : i686-pc-linux-gnu (Redhat 7.1)
> to build powerpc-linux-gnu cross gcc 3.0.4, with binutils 2.12
> ./configure --target=powerpc-ibm-linux-gnu --with-newlib
You shouldn't use newlib if you're targeting a specific OS; you should
install or build headers and libraries specific to the OS. In this case,
you should build glibc for your target or extract the headers and basic
libraries from a binary PPC gnu/linux distribution. I'm afraid I don't
know the specifics of doing this; you might have to build a powerpc-elf
cross-compiler using newlib and then use that to build glibc for
powerpc-linux-gnu, or there might be an easier way (integrate glibc into
the sources tree and build in parallel?) but I'm not sure.
In addition to glibc, you'll also need the linux/ and asm/ headers from
the kernel source.
> seeing errors of files not exist while compiling in rs6000/linux.h
> about <signal.h> and <sys/ucontext.h>, while there are such files
> right there under /usr/include.
These headers belong to the compile host and should not be used for the
cross target. In you case, it's using only the headers provided with
newlib.
Good luck,
Rup.
next parent reply other threads:[~2002-04-18 18:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <616BE6A276E3714788D2AC35C40CD18D5B2A8F@whale.softwire.co.uk>
2002-04-18 17:15 ` Rupert Wood [this message]
2002-04-18 11:51 Harry Lin
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=616BE6A276E3714788D2AC35C40CD18D120075@whale.softwire.co.uk \
--to=me@rupey.net \
--cc=gcc-help@gcc.gnu.org \
--cc=hlin@hauppauge.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 read-only IMAP folder(s) and NNTP newsgroup(s).