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] libstdc++ with external toolchain
Date: Sun, 25 Oct 2009 22:21:36 +0100	[thread overview]
Message-ID: <20091025222136.14fe0c62@surf> (raw)
In-Reply-To: <d459bb380910160851r2481b32dy3f25a9379dd2c0a6@mail.gmail.com>

Hello Marco,

Le Fri, 16 Oct 2009 17:51:40 +0200,
Marco Braga <marco.braga@gmail.com> a ?crit :

> I am successfully using buildroot-2009.08 with external toolchain from
> CodeSourcery, but I have a problem with the "Build/install c++
> compiler and libstdc++?" option that sets BR2_INSTALL_LIBSTDCPP.
> Basically the libstdc++ is not installed because buildroot expects
> this to be in "lib" directory of the toolchain instead of "usr/lib"
> (as is in CodeSourcery's toolchain for ARM).
> 
> I'd like to understand if this is the expected behavior or it is a
> bug.

Supporting all sort of external toolchains is difficult, and I
initially started adding external toolchain support to Buildroot by
testing toolchains generated by Crosstool-NG. Supporting Codesourcery
toolchains is on my TODO-list.

Could you submit a bug report so that I can keep track of this issue,
and fix it when I'll work again on Codesourcery toolchains support ?

Thanks!

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

      reply	other threads:[~2009-10-25 21:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-16 15:51 [Buildroot] libstdc++ with external toolchain Marco Braga
2009-10-25 21:21 ` Thomas Petazzoni [this message]

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=20091025222136.14fe0c62@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