Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Emil Krüper" <e.krueper@solcon-systemtechnik.de>
To: buildroot@busybox.net
Subject: [Buildroot] Glibc instead of uclibc
Date: Thu, 06 Mar 2008 08:12:26 +0100	[thread overview]
Message-ID: <1204787546.28258.21.camel@PC-EK.Solcon> (raw)
In-Reply-To: <c05908680803050933p15ae7f46y77a16d3af3262e45@mail.gmail.com>

In the toolchain menu select external toolchain. Next you should go to
the external toolchain options and change the external toolchain path
to /usr and the external toolchain prefix to i386-linux-gnu. Just to be
safe have a look at /usr/bin/, depending on your distribution it might
be i486, i586 or i686. Modify the external toolchain prefix accordingly.
If there is something missing at compile time, create a symbolic link
from the appropriate binary to /usr/bin/ix86-linux-gnu-xxx. That usually
happens the first times you run your buildroot with your systems
toolchain.

Best regards
Emil Kr?per


On Wed, 2008-03-05 at 18:33 +0100, Salvatore Fassi wrote:
> No, I'm not searching for an arm/mipsel toolchain...I need only a
> simple i386 toolchain, that's why I wanted to use the one from my
> linux pc.
> However thank you for the suggestion...it will be useful for the
> future!
> 
> Salvo
> 
> On Wed, Mar 5, 2008 at 6:23 PM, JS <js@hipro.co.in> wrote:
>         On Wed, 2008-03-05 at 18:16 +0100, Salvatore Fassi wrote:
>         > So is not possible to use the toolchain that is currently
>         installed on
>         > my linux pc?
>         > Must I download binutils, gcc etc etc to compile a brand new
>         toolchain
>         > (following the instructions provided in some cross-compiler
>         how-to)?
>         
>         
>         If you are lookin for a arm/mipsel toolchain, you should
>         checkout eldk.
>         I am sure you can use ELDK along with buildroot..
>         
>         --
>         HiPro Solutions
>         http://hipro.co.in/
>         
>         
>         
>         _______________________________________________
>         buildroot mailing list
>         buildroot at uclibc.org
>         http://busybox.net/mailman/listinfo/buildroot
>         
> 
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
-- 
Mit freundlichen Gr??en


Emil Kr?per

Solcon Systemtechnik GmbH
Niels-Bohr-Ring 3-5
23568 L?beck

Tel.: (0451)-40948-19
Fax.: (0451)-40948-88
Email: e.krueper at solcon-systemtechnik.de
www.solcon-systemtechnik.de

Sitz der Gesellschaft: L?beck
Amtsgericht: L?beck | HRB 3662
Gesch?ftsf?hrer: Dr.-Ing. Reiner Wieck, Dr.-Ing. Gerd Schneider


Der Inhalt dieser E-Mail ist vertraulich und oder rechtlich gesch?tzt,
und damit ausschlie?lich f?r den bezeichneten Adressaten bestimmt. Wenn
Sie nicht der vorgesehene Adressat dieser E-Mail oder dessen Vertreter
sein sollten, so beachten Sie bitte, dass jede Form der Kenntnisnahme,
Ver?ffentlichung, Vervielf?ltigung oder Weitergabe des Inhalts dieser
E-Mail unzul?ssig ist. Wir bitten Sie, sich in diesem Fall mit dem
Absender in Verbindung zu setzen und diese E-Mail und jeden Anhang von
Ihrem System zu l?schen. Vielen Dank.

  reply	other threads:[~2008-03-06  7:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05 15:44 [Buildroot] Glibc instead of uclibc Salvatore Fassi
2008-03-05 16:59 ` sjhill at realitydiluted.com
2008-03-05 17:16   ` Salvatore Fassi
2008-03-05 17:23     ` JS
2008-03-05 17:33       ` Salvatore Fassi
2008-03-06  7:12         ` Emil Krüper [this message]
2008-03-06  7:27           ` Salvatore Fassi
2008-03-06  9:25             ` Salvatore Fassi
2008-03-07 17:18               ` Salvatore Fassi
2008-03-07 18:17                 ` sjhill at realitydiluted.com
2008-03-05 17:23     ` Rex Ashbaugh
2008-03-05 17:27       ` Salvatore Fassi
2008-03-05 17:28     ` sjhill at realitydiluted.com
  -- strict thread matches above, loose matches on Subject: below --
2012-08-03 14:47 [Buildroot] glibc " Zoran Djordjevic

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=1204787546.28258.21.camel@PC-EK.Solcon \
    --to=e.krueper@solcon-systemtechnik.de \
    --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