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] Foreigh toolchain
Date: Thu, 24 Sep 2009 20:28:01 +0200	[thread overview]
Message-ID: <20090924202801.78a69428@surf> (raw)
In-Reply-To: <185890.9723.qm@web23501.mail.ird.yahoo.com>

Le Thu, 24 Sep 2009 16:33:13 +0000 (GMT),
Michael Trimarchi <trimarchimichael@yahoo.it> a ?crit :

> I have this problem using the foreigh toolchain. Can anyone know how
> to fix it?

That's a libtool issue, and I haven't yet found the proper solution for
it. It's probably a matter of recompiling libtool and using our own.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2009-09-24 18:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-23 10:08 [Buildroot] Problem with defconfig Mark Jackson
2009-09-23 10:24 ` Peter Korsgaard
2009-09-23 10:53   ` Mark Jackson
2009-09-23 11:05     ` Peter Korsgaard
2009-09-23 11:13       ` Mark Jackson
2009-09-23 12:41         ` Peter Korsgaard
2009-09-23 12:45           ` Mark Jackson
2009-09-23 13:01             ` Peter Korsgaard
2009-09-23 14:09               ` Mark Jackson
2009-09-23 20:03                 ` Peter Korsgaard
2009-09-24 10:50           ` Mark Jackson
2009-09-24 15:42             ` Thiago A. Corrêa
2009-09-24 15:48               ` Peter Korsgaard
2009-09-24 16:33                 ` [Buildroot] Foreigh toolchain Michael Trimarchi
2009-09-24 18:28                   ` Thomas Petazzoni [this message]
2009-09-25  7:35                     ` Michael Trimarchi
2009-09-24 10:45   ` [Buildroot] Problem with defconfig Mark Jackson
  -- strict thread matches above, loose matches on Subject: below --
2009-12-08 20:16 [Buildroot] Foreigh toolchain Michael Trimarchi

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=20090924202801.78a69428@surf \
    --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