Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-05-22
Date: Wed, 28 May 2014 08:43:11 +0200	[thread overview]
Message-ID: <20140528084311.05629fce@free-electrons.com> (raw)
In-Reply-To: <20140528063024.GA3510@free.fr>

Dear Yann E. MORIN,

On Wed, 28 May 2014 08:30:24 +0200, Yann E. MORIN wrote:

> >  A proper solution would be to adapt our libtool patches to interpret -static as
> > -all-static. Or alternatively, to patch the compiler wrapper to interpret
> > -all-static as -static (and then of course we'd have to generalize the compiler
> > wrapper to also use it for internal toolchains).
> 
> Yes, I think this is a good idea. But we can't use the wrapper to build
> the toolchain itself, of course.

And there is no wrapper at all when we use the internal toolchain
backend. At least as of today.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-05-28  6:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-05-22 Thomas Petazzoni
2014-05-23  9:32 ` Fabio Porcedda
2014-05-23 17:08   ` Thomas Petazzoni
2014-05-28  6:10     ` Arnout Vandecappelle
2014-05-28  6:30       ` Yann E. MORIN
2014-05-28  6:43         ` Thomas Petazzoni [this message]
2014-05-28  6:47           ` Yann E. MORIN
2014-05-28  7:06             ` Thomas Petazzoni
2014-05-28  8:05               ` Peter Korsgaard

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=20140528084311.05629fce@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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