[pocket-linux] Chapter 3. The dreaded libc.so.6

[Miguel Angel Servin Velazquez]

Hi.
I tried that too.
I put the library in /lib/tls in my root disk.
It did not work.
Then I put the library in /lib and created a symlink to it in /lib/tls and still no go.

How can I build bash and tell it to look for libc.so.6 in /lib instead to /lib/tls?

Thanks.

-----Original Message-----
From: pocket-linux-bounces at ufo.chicago.il.us [mailto:pocket-linux-bounces at ufo.chicago.il.us] On Behalf Of Phil Birkelbach
Sent: Miércoles, 27 de Octubre de 2004 03:26 p.m.
To: Miguel Servin; Support for Pocket Linux Guide
Subject: Re: [pocket-linux] Chapter 3. The dreaded libc.so.6

It's been a while since I went through the guide but I think your answer 
is in your question.  You said the output of ldd on bash is 
/lib/tls/libc.so.6  You should have a /lib/tls directory on your root 
disk with libc.so.6 (or a symlink) in that directory.  Or rebuild bash 
so that it is looking in /lib for libc.so.6

Godspeed,

Phil Birkelbach - Houston Texas
RV-7 N727WB (Reserved) - Panel
http://www.myrv7.com



Miguel Servin wrote:

>Hi folks.
>
>I recently decided to build the pocket-linux and I have to say it is a
>very educational and enjoyable experience. :)...until chapter 3.
>
>I'm experiencing problems trying to build my chapter 3 rootdisk,
>because every time the kernel try to load /bin/sh, it panics and die:
>
>Init (or /bin/sh): error while loading shared libraries: libc.so.6:
>cannot open shared object file: No such file or directory.
>
>I know is not the ramdisk support on my kernel, because my boot disk
>can use the rootdisk image from the pocket-linux home page. (and
>viceversa: the bootdisk from the homepage dies with the same error
>when using my rootdisk.)
>
>I've reading the archives, searching the web, and I can find some
>other people who gets the same error message, but I can't seem to find
>a solution. (that...combined with the fact that I'm pretty new to
>Linux)
>
>Whether I compile Bash 2.05a or 3.0, I get the same error.
>I even tried not targeting for i386, but still no go. (not exporting
>the CC variable and omitting the --host= parameter) It just can' find
>the library.
>Leaving the libraries unstripped didn't work.
>The file permissions are ok, (0755) (and yes, I checked the libraries
>are not just the symlinks from my original /lib)
>I even created symlinks to the libraries in /bin, but still no go.
>
>NO SUCH FILE OR DIRECTORY.
>
>The output from ldd tells me that bash uses /lib/tls/libc.so.6 so I
>used that first, and then with the one in /lib but nothing.
>
>To me, somehow the binary can't find the library, and I just don't
>why... even if the libraries are there... where they're supposed to
>be. Maybe it's something very simple, like setting a variable when
>doing the compile or something like that, but honestly I don't know
>what.
>
>I don't want to use the disk image from the homepage because I would
>like to do the actual building myself (that's what this project is
>about, right?), and besides I think I can run into the same problems
>when building the rest of the utils, so I need to know what to tweak.
>
>I'm using a disconnected RedHat 9 box for the project (No updates or
>patches), on a PIII 500Mhz, thought it was broken, but no. :)
>
>I hope someone can point me to the right direction.
>
>Thank you very much.
>
>El Servas.
>
>_______________________________________________
>Pocket-Linux mailing list
>Pocket-Linux at ufo.chicago.il.us
>http://ufo.chicago.il.us/cgi-bin/mailman/listinfo/pocket-linux
>  
>

_______________________________________________
Pocket-Linux mailing list
Pocket-Linux at ufo.chicago.il.us
http://ufo.chicago.il.us/cgi-bin/mailman/listinfo/pocket-linux




...........................................................................................
Este correo electronico es confidencial y/o puede contener informacion privilegiada.
Si usted no es su destinatario o no es alguna persona autorizada por este para recibir sus correos electronicos, NO debera usted utilizar, copiar, revelar, o tomar ninguna accion basada en este correo electronico o cualquier otra informacion incluida en el, favor de notificar al remitente de inmediato mediante el reenvio de este correo electronico y borrar a continuacion totalmente este correo electronico y sus anexos.
Nota: Los acentos y caracteres especiales fueron omitidos para su correcta lectura en cualquier medio electronico.

This e-mail is confidential and/or may contain privileged information.
If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any
other information herein, please advise the sender immediately by reply this e-mail and delete this e-mail and  its attachments. 
...........................................................................................


...........................................................................................
Este correo electronico es confidencial y/o puede contener informacion privilegiada.
Si usted no es su destinatario o no es alguna persona autorizada por este para recibir sus correos electronicos, NO debera usted utilizar, copiar, revelar, o tomar ninguna accion basada en este correo electronico o cualquier otra informacion incluida en el, favor de notificar al remitente de inmediato mediante el reenvio de este correo electronico y borrar a continuacion totalmente este correo electronico y sus anexos.
Nota: Los acentos y caracteres especiales fueron omitidos para su correcta lectura en cualquier medio electronico.

This e-mail is confidential and/or may contain privileged information.
If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any
other information herein, please advise the sender immediately by reply this e-mail and delete this e-mail and  its attachments. 
...........................................................................................