public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Esben Haabendal <esben.haabendal@dev.prevas.dk>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: crossgcc@sourceware.org
Subject: Re: Request for testing: canadian rework
Date: Tue, 24 Apr 2012 18:58:00 -0000	[thread overview]
Message-ID: <878vhlj6tu.fsf@dev.prevas.dk> (raw)
In-Reply-To: <201204232324.48346.yann.morin.1998@free.fr> (Yann E. MORIN's	message of "Mon, 23 Apr 2012 23:24:48 +0200")

"Yann E. MORIN" <yann.morin.1998@free.fr> writes:

> Esben, All,
>
> On Saturday 21 April 2012 20:45:24 Esben Haabendal wrote:
>> "Yann E. MORIN" <yann.morin.1998@free.fr> writes:
>> 
>> > Changes (from 4.000 feet high):
>> >   - no need for a pre-exisiting x-compiler for the target
>> >   - a complete x-compiler for target is built for internal use, but is not
>> >     exported for the user to use
>> 
>> Will it still be possible to use a pre-existing x-compiler for target?
>> 
>> When building let's say 3 canadian-cross crompilers, fx.
>> 
>> i686-linux -> arm-linux
>> x86_64-linux -> arm-linux
>> mingw32 -> arm-linux
>> 
>> It would be nice to be able to not have to build the same target
>> x-compiler three times.
>
> Ah, I did not think of this use-case... No, the new infra will not allow
> that. The whole purpose was to get rid of the separate cross-compiler build,
> to be able to build the canadian cross in one run (except of course the
> cross- compiler for the host which is needed anyway to cross-build all the
> other stuff for the host).
>
> I believe this will be easy to re-add in the next release, though. The code
> was there anyway, it's just a matter to re-enable it.
>
> Thanks for the suggestion!

Great, I will look forward to that, so I don't have to get stuck on an
old version of ct-NG :-)

/Esben

--
For unsubscribe information see http://sourceware.org/lists.html#faq

  reply	other threads:[~2012-04-24 18:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16 21:55 Yann E. MORIN
2012-04-21 18:46 ` Esben Haabendal
2012-04-23 21:25   ` Yann E. MORIN
2012-04-24 18:58     ` Esben Haabendal [this message]
2012-08-06  6:32     ` Esben Haabendal
2012-08-06 17:01       ` Yann E. MORIN
2012-08-06 18:50         ` Esben Haabendal

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=878vhlj6tu.fsf@dev.prevas.dk \
    --to=esben.haabendal@dev.prevas.dk \
    --cc=crossgcc@sourceware.org \
    --cc=yann.morin.1998@free.fr \
    /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).