[Buildroot] Glibc instead of uclibc

[Buildroot] Glibc instead of uclibc

[Salvatore Fassi]

Hi all,
This is my first mail in here.
Is there a way to use glibc instead of uclibc in buildroot?
I've found some old patches (february 2007) but now they don't match against
new files:
http://bugs.uclibc.org/view.php?id=237

Can someone help me?
Thanks.

Salvatore
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20080305/fc50d781/attachment.htm 

[Buildroot] Glibc instead of uclibc

[sjhill at realitydiluted.com]

The only way to use glibc is to build an external glibc toolchain and
then specify using an external toolchain in buildroot.

-Steve

[Buildroot] Glibc instead of uclibc

[Salvatore Fassi]

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)?


On Wed, Mar 5, 2008 at 5:59 PM, <sjhill@realitydiluted.com> wrote:

> The only way to use glibc is to build an external glibc toolchain and
> then specify using an external toolchain in buildroot.
>
> -Steve
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20080305/4836dbce/attachment.htm 

[Buildroot] Glibc instead of uclibc

[JS]

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] Glibc instead of uclibc

[Rex Ashbaugh]

yes and yes.
unless you can find a suitable pre-built cross glibc toolchain somewhere
online.

-Rex

On 3/5/08, Salvatore Fassi <salvatore.fassi@gmail.com> 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)?
>
>
> On Wed, Mar 5, 2008 at 5:59 PM, <sjhill@realitydiluted.com> wrote:
>
> > The only way to use glibc is to build an external glibc toolchain and
> > then specify using an external toolchain in buildroot.
> >
> > -Steve
> >
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20080305/347dd65c/attachment-0001.htm 

[Buildroot] Glibc instead of uclibc

[Salvatore Fassi]

Ok!
Thank you all for these useful information!

Salvo

On Wed, Mar 5, 2008 at 6:23 PM, Rex Ashbaugh <rexa@xeratech.com> wrote:

> yes and yes.
> unless you can find a suitable pre-built cross glibc toolchain somewhere
> online.
>
> -Rex
>
> On 3/5/08, Salvatore Fassi <salvatore.fassi@gmail.com> 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)?
> >
> >
> > On Wed, Mar 5, 2008 at 5:59 PM, <sjhill@realitydiluted.com> wrote:
> >
> > > The only way to use glibc is to build an external glibc toolchain and
> > > then specify using an external toolchain in buildroot.
> > >
> > > -Steve
> > >
> >
> >
> > _______________________________________________
> > buildroot mailing list
> > buildroot at uclibc.org
> > http://busybox.net/mailman/listinfo/buildroot
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20080305/5ce50e1e/attachment.htm 

[Buildroot] Glibc instead of uclibc

[sjhill at realitydiluted.com]

> 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)?
> 
You can certainly use your installed toolchain, yes. Configure buildroot
to use an external toolchain, specify a prefix of '/usr/bin' for the
toolchain/compiler and see what happens.

-Steve

[Buildroot] Glibc instead of uclibc

[Salvatore Fassi]

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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20080305/a6569b76/attachment.htm 

[Buildroot] Glibc instead of uclibc

[Emil Krüper]

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.

[Buildroot] Glibc instead of uclibc

[Salvatore Fassi]

Thank you Emil!
This is a great answer!
I'm trying now...I let you know if I will be able to compile everything!

Salvo

2008/3/6 Emil Kr?per <e.krueper@solcon-systemtechnik.de>:

> 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.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20080306/3560dd2f/attachment-0001.htm 

[Buildroot] Glibc instead of uclibc

[Salvatore Fassi]

Yes!!
It works!
Thank you all again!

Salvo

2008/3/6 Salvatore Fassi <salvatore.fassi@gmail.com>:

> Thank you Emil!
> This is a great answer!
> I'm trying now...I let you know if I will be able to compile everything!
>
> Salvo
>
> 2008/3/6 Emil Kr?per <e.krueper@solcon-systemtechnik.de>:
>
> 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.
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20080306/8ebbbd03/attachment.htm 

[Buildroot] Glibc instead of uclibc

[Salvatore Fassi]

Hi all,
I'm here again.

I had been able to compile a complete rootfs with xorg and gtk and to boot
it, but I had to copy libcrypt, libm and ld-linux.so (with all their links
etc etc) manually because on my rootfs /lib there was only libc.
Now the system boots ok...but I can't login!!
I've tried using "root" with various passwords (also empty one) but I'm
still not able to log in...

Am I missing some other libraries? Why do all these libraries weren't copied
in the rootfs automatically?  :-/
P.S : For your information...I'm using my linux pc toolchain (fedora core 6)
as an external toolchain for buildroot.

Salvo


2008/3/6 Salvatore Fassi <salvatore.fassi@gmail.com>:

> Yes!!
> It works!
> Thank you all again!
>
> Salvo
>
> 2008/3/6 Salvatore Fassi <salvatore.fassi@gmail.com>:
>
> Thank you Emil!
> > This is a great answer!
> > I'm trying now...I let you know if I will be able to compile everything!
> >
> > Salvo
> >
> > 2008/3/6 Emil Kr?per <e.krueper@solcon-systemtechnik.de>:
> >
> > 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.
> > >
> > >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20080307/7b5a2d78/attachment-0001.htm 

[Buildroot] Glibc instead of uclibc

[sjhill at realitydiluted.com]

On Fri, Mar 07, 2008 at 06:18:52PM +0100, Salvatore Fassi wrote:
> 
> I had been able to compile a complete rootfs with xorg and gtk and to boot
> it, but I had to copy libcrypt, libm and ld-linux.so (with all their links
> etc etc) manually because on my rootfs /lib there was only libc.
> Now the system boots ok...but I can't login!!
> I've tried using "root" with various passwords (also empty one) but I'm
> still not able to log in...
> 
> Am I missing some other libraries? Why do all these libraries weren't copied
> in the rootfs automatically?  :-/
> P.S : For your information...I'm using my linux pc toolchain (fedora core 6)
> as an external toolchain for buildroot.
> 
You are missing the other libraries. Here is what my buildroot config
options look like for my buildroot using an external glibc toolchain:

BR2_TOOLCHAIN_EXTERNAL_LIB_C="libc.so.6"
BR2_TOOLCHAIN_EXTERNAL_LIBS="ld.so.1 libcrypt.so libdl.so libgcc_s.so libm.so libnsl.so libnss_dns.so libnss_files.so libpthread.so libresolv.so librt.so libstdc++.so libutil.so"

The libraries that you do not have which are preventing you from logging
in our 'libnsl.so' and 'libnss_dns.so' and 'libnss_file.so'. Once those
are in your root filesystem, you will be able to login.

-Steve

[Buildroot] glibc instead of uclibc

[Zoran Djordjevic]

Excuse me once more for mail mess. No I quit - going on vacation, 
and probably will quit with all those stuffs, especially because it was
only theoretical.
Maybe I will obay you and learn Qt programming - who knows.
?
Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120803/e924edd5/attachment.html>