public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
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: Fri, 05 Dec 1997 10:44:00 -0000	[thread overview]
Message-ID: <24779.881340876@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?
Either is correct (IMHO), though as you note they must be consistent!

The first is a little simpler -- there's a nice place where one can go
and find the target libraries, target includes and binaries suitable for
compiling and examining target objects.

The second is also good in that you could have different sets of include
files for different versions of cross compilers for the target.

I believe Cygnus uses the first version internally, but I don't want to 
force that convention on everyone if it doesn't make sense.



jeff

  reply	other threads:[~1997-12-05 10:44 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 [this message]
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=24779.881340876@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).