From: Mike Neuhauser <mike@gams.co.at>
To: law@cygnus.com
Cc: egcs@cygnus.com
Subject: Re: --with-headers for cross-compile broken? (egcs-971201)
Date: Wed, 03 Dec 1997 03:30:00 -0000 [thread overview]
Message-ID: <199712031110.MAA13120@scully.gams.co.at> (raw)
In-Reply-To: <3893.881090739@cygnus.com>
In message < 3893.881090739@cygnus.com >, Jeffrey A Law writes:
> 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
CROSS_COMPILE is defined. I tracked the problem down now,
egcs-971201/configure.in and egcs-971201/gcc/Makefile.in don't agree on
the location for the cross headers:
configure (see egcs-971201/configure.in) copies the headers to
${prefix}/${target_alias}/sys-include
while egcs-971201/gcc/Makefile.in defines CROSS_INCLUDE_DIR to be
$(libsubdir)/sys-include
with libsubdir = $(libdir)/gcc-lib/$(target_alias)/$(version)
So these two directories are clearly different, but which one is the
right one?
--
Michael Neuhauser Phone: +43(1)8958499/17
g.a.m.s. edv-dienstleistungen gmbh Fax: +43(1)8958499/60
Stiegergasse 15-17/8 Email: mike@gams.at
A-1150 Vienna/Austria/Europe
next prev parent reply other threads:[~1997-12-03 3:30 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
1997-12-03 3:30 ` Mike Neuhauser [this message]
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=199712031110.MAA13120@scully.gams.co.at \
--to=mike@gams.co.at \
--cc=egcs@cygnus.com \
--cc=law@cygnus.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).