public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Eric Botcazou <ebotcazou@adacore.com>
To: Iain Sandoe <iain@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, Arnaud Charlet <charlet@adacore.com>
Subject: Re: [Patch Ada/build] deal with some cross/native cross issues
Date: Wed, 06 Nov 2013 13:13:00 -0000	[thread overview]
Message-ID: <1757219.DocZddhPPW@polaris> (raw)
In-Reply-To: <66B73BAF-77A5-46B4-9D81-9043E7F17BAA@codesourcery.com>

> I've been trying to improve the building and testing of Darwin for crosses
> and native crosses.
> 
> This has thrown up a few small glitches in the Ada build stuff (that would
> seem to apply to any build-host-nativeX scenario, not just darwin).  I
> would imagine it would be beneficial to resolve these, since Ada requires
> Ada - a native cross seems like the only realistic way onto a new target.

Thanks for working on this.

> 1. xgnatugn needs to be run on the build system, so needs to be built with
> the build system's gnatmake. I haven't put a canonical prefix on this since
> this doesn't appear to be done elsewhere. Defined as GNATMAKE_FOR_BUILD and
> passed to sub-processes.

Why do you need to pass it to ADA_TOOLS_FLAGS_TO_PASS though?  Just replace 
$(GNATMAKE) with gnatmake.

> 2. Some builds might need to pass LDFLAGS to the gnat* builds.  Appended
> LDFLAGS to GCC_LINK.  Passed on in gnattools/Make.

OK.

> 3. In gnattools, the RTS dir must be for the host and not for the build; 
> This actually only showed up when I tried a cross from a 64bit pointer
> machine to a 32bit pointer one (i.e it is easy for it to go unnoticed).

OK, but don't you need to do the same for gnatmake/gnatbind/gnatlink here?
See gcc-interface/Make-lang.in, line 171 and below, for similar code.

-- 
Eric Botcazou

  reply	other threads:[~2013-11-06 12:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-03 21:35 Iain Sandoe
2013-11-06 13:13 ` Eric Botcazou [this message]
2013-12-11 14:48   ` Iain Sandoe

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=1757219.DocZddhPPW@polaris \
    --to=ebotcazou@adacore.com \
    --cc=charlet@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=iain@codesourcery.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).