From: Harry Lin <hlin@hauppauge.com>
To: gcc-help@gcc.gnu.org
Subject: build cross gcc for ppc-linux
Date: Thu, 18 Apr 2002 11:51:00 -0000 [thread overview]
Message-ID: <02041814423805.13119@coyote> (raw)
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
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.
searching the archieves of gcc mailing lists, there were reports of such
problems, but no one posted answers
although i can get into rs6000/linux.h to try to hack around, i bet this is a
problem that must have been fixed gracefully,
any one knows sth about this....Thanx
Harry
next reply other threads:[~2002-04-18 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 11:51 Harry Lin [this message]
[not found] <616BE6A276E3714788D2AC35C40CD18D5B2A8F@whale.softwire.co.uk>
2002-04-18 17:15 ` Rupert Wood
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=02041814423805.13119@coyote \
--to=hlin@hauppauge.com \
--cc=gcc-help@gcc.gnu.org \
/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).