From: Jeffrey A Law <law@cygnus.com>
To: Mike Neuhauser <mike@gams.co.at>
Cc: egcs@cygnus.com
Subject: Re: --with-headers for cross-compile broken? (egcs-971201)
Date: Tue, 02 Dec 1997 11:25:00 -0000 [thread overview]
Message-ID: <3893.881090739@cygnus.com> (raw)
In-Reply-To: <199712021615.RAA11779@scully.gams.co.at>
In message < 199712021615.RAA11779@scully.gams.co.at >you write:
> I'm trying to build a powerpc-unknown-linux-gnulibc2 targeted cross
> compiler on an i686-pc-linux-gnulibc1 host. I've got problems with the
> target header files.
>
> I'm using bintuls-2.8.1.0.17 (binutils and egcs are built together)
> and egcs-971201 (egcs-971122 shows same behaviour).
> The following sets up the build directory and does the build:
Hmmm, the include search path didn't look correct.
The first thing I would do is make sure CROSS_COMPILE is being defined
when building cccp.c.
Jeff
next prev parent reply other threads:[~1997-12-02 11:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-02 9:56 Mike Neuhauser
1997-12-02 11:25 ` Jeffrey A Law [this message]
1997-12-03 3:30 ` Mike Neuhauser
1997-12-05 10:44 ` Jeffrey A Law
1998-02-24 19:54 ` Jeffrey A Law
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=3893.881090739@cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=mike@gams.co.at \
/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).