PeeWeeLinux 0.61 with glibc 2.2.5 on PC/104. Problems with

Do you have a question? Post it now! No Registration Necessary

Translate This Thread From English to

Threaded View

I'm currently trying to port a PeeWeeLinux 0.61, a Java Runtime
Environment  IBM-Java2-JRE-1.3.1 and a Tomcat Webserver to a PC/104

IBM-Java2-JRE-1.3.1 requires at least glibc 2.2.4. I've replace the
files of glibc 2.1.3 of the PeeWeeLinux 0.61 with files from glibc

When trying to boot the PC/104 board I get the following message:
: error in loading shared libraries: cannot open shared
object file: No such file or directory is located in /lib

Can anybody help?


Re: PeeWeeLinux 0.61 with glibc 2.2.5 on PC/104. Problems with

Quoted text here. Click to load it

It may be looking at /lib/i686 (or lower depending on your
proc). That's where it is on my RH box. On your host machine,
try applying:
objdump -x <program> | grep RPATH
to the binaries you installed.

Quoted text here. Click to load it

We've slightly trimmed the long signature. Click to see the full one.
Re: PeeWeeLinux 0.61 with glibc 2.2.5 on PC/104. Problems with
My Proc is 486
/lib/ix86 does not exist on PeeWeeLinux

Contents of /lib of PeeWeeLinux 0.61: -> -> -> -> -> -> -> -> -> -> -> -> ->

Contents of /lib were replace by the following libraries of glibc

objdump -x | grep RPATH
gives no output.

Do I have to set RPATH somewhere, although /lib is the default
directory for libraries?


Re: PeeWeeLinux 0.61 with glibc 2.2.5 on PC/104. Problems with

Here's what I'd do:
- start with a fresh install of the distribution and check that it boots
- add the additionnal programs, one at a time, and check the system boots after
each addition
- when you have found the program "foo" that fails, run it through ldd and
objdump on the system
you've copied it from:

$ ldd foo
$ objdump -x foo

ldd shows the exact path of the libraries that "foo" depends on, on the host
system. These libraries
depend both on some definitions inside "foo", and on the way the host system is
installed. It may be that
you have several instances of and only one provides the version that
foo requires. On doubt,
ldconfig may also provide some hints:

$ ldconfig -p | grep (libc6, hwcap: 0x8000000000000, OS ABI: Linux 2.4.1) =>
/lib/i686/ (libc6, OS ABI: Linux 2.2.5) => /lib/

(redhat 8.0) shows that the one in lib/`uname -m` has a specific hardware
definition, and supports
a more recent ABI.

objdump shows foo's definitions, especially the exact libs that it depends on,
as well as
the RPATH/RUNPATH fieds (see "man" for explanations). It may be (though it
is bad
practice) that a shared object dependency is included as a complete path.

Hope this helps,


firstname dot lastname at jaluna dot com

Site Timeline