public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Peter Bergner <bergner@vnet.ibm.com>
To: Bernd Edlinger <bernd.edlinger@hotmail.de>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	       David Edelsohn	 <dje@gcc.gmail.com>,
	       Michael Meissner <meissner@linux.vnet.ibm.com>
Subject: Re: [PATCH configure,config.gcc] Fix for PR69153 to allow config.gcc to set target_header_dir
Date: Sun, 10 Jan 2016 23:10:00 -0000	[thread overview]
Message-ID: <1452467429.5201.20.camel@vnet.ibm.com> (raw)
In-Reply-To: <HE1PR07MB090530387C9DF47DCA4DE50AE4C80@HE1PR07MB0905.eurprd07.prod.outlook.com>

On Sun, 2016-01-10 at 19:28 +0000, Bernd Edlinger wrote:
> Hi Peter,
> 
> > @@ -4167,6 +4167,7 @@
> > 			-d "/opt/$with_advance_toolchain/bin/." -a \
> > 			-d "/opt/$with_advance_toolchain/include/.";
> > then
> > 
> > +			target_header_dir=`find
> > /opt/$with_advance_toolchain/ -path '*/include/features.h' | sed -e
> > 's#/features.h##'`
> > 			tm_file="$tm_file ./advance-toolchain.h"
> > 			(at="/opt/$with_advance_toolchain"
> > 			 echo "/* Use Advance Toolchain $at */"
> 
> why can't you just set native_system_header_dir instead?
> 

That won't work on our cross builds using --with-advance-toolchain=...
options, correct?  And don't we really need the native_system_header_dir
to really point at the native system headers for tests against gmp.h etc.?

Peter

  reply	other threads:[~2016-01-10 23:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-10 19:28 Bernd Edlinger
2016-01-10 23:10 ` Peter Bergner [this message]
2016-01-11 19:20   ` Michael Meissner
2016-01-11 21:36     ` Bernd Edlinger
2016-01-20  0:46       ` Peter Bergner
  -- strict thread matches above, loose matches on Subject: below --
2016-01-10 17:44 Peter Bergner

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=1452467429.5201.20.camel@vnet.ibm.com \
    --to=bergner@vnet.ibm.com \
    --cc=bernd.edlinger@hotmail.de \
    --cc=dje@gcc.gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=meissner@linux.vnet.ibm.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).