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, 24 Feb 1998 19:54:00 -0000 [thread overview]
Message-ID: <1785.888376736@hurl.cygnus.com> (raw)
In-Reply-To: <199712031110.MAA13120@scully.gams.co.at>
In message <199712031110.MAA13120@scully.gams.co.at>you write:
> 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?
This has been fixed for the upcoming 1.0.2 release as well as in the
mainline sources.
We're using ${prefix}/${target_alias}/sys-include
jeff
prev parent reply other threads:[~1998-02-24 19:54 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
1997-12-05 10:44 ` Jeffrey A Law
1998-02-24 19:54 ` Jeffrey A Law [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=1785.888376736@hurl.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).