Greetings Harri. Before I started playing with the export command, I had this problem. Here is the output: ----------------------------------------------------------------------------------------- [EMAIL PROTECTED]:/$ bash -x /usr/sbin/mkinitrd ... + set -e ++ pwd + ORIGDIR=/ + PROG=/usr/sbin/mkinitrd + CONFDIR=/etc/mkinitrd + unset keep croot cmkimage out + getopts d:km:o:r: flag + shift 0 + '[' ']' + usage + revision='$Id: mkinitrd,v 1.201 2004/05/16 22:00:48 herbert Exp $' + cat $Id: mkinitrd,v 1.201 2004/05/16 22:00:48 herbert Exp $ Usage: /usr/sbin/mkinitrd [OPTION]... <-o outfile> [version] Options: -d confdir Specify an alternative configuration directory. -k Keep temporary directory used to make the image. -m command Set the command to make an initrd image. -o outfile Write to outfile. -r root Override ROOT setting in mkinitrd.conf. See mkinitrd(8) for further details. + exit 1 ------------------------------------------------------------------------------------------- gcc --version gcc (GCC) 3.3.5 (Debian 1:3.3.5-5) Copyright (C) 2003 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. ------------------------------------------------------------------------------------------ I have noticed that ldd and mkinitrd seem not to packages unto themselves, otherwise I would have re-installed them. Can you interpret this? Thank you. Chris W. On December 22, 2004 09:43 pm, Harald Dunkel wrote: > Chris Wakefield wrote: > | using: /usr/sbin/mkinitrd -o initrd.img-2.6.10-rc3 2.6.10-rc3 > | I'm now getting: > | /bin/bash: error while loading shared libraries: libdl.so.2: cannot open > | shared object file: No such file or directory > > Sorry, but I cannot reproduce this (using > amd64 (gcc-3.4)). There are no platform > dependent binaries in initrd-tools, so the > problem must be in the environment. > > But mkinitrd uses ldd to get a list of > libraries to add to the initrd.img. > > Do you have some environment variables set > affecting shared library handling (e.g. > LD_PRELOAD, LD_LIBRARY_PATH, LD_RUNPATH)? > > Maybe you could run > > bash -x /usr/sbin/mkinitrd ... > > to see what goes wrong in mkinitrd? > > > Regards > > Harri |
- Re: mkinitrd linking issue. Chris Wakefield
- Re: mkinitrd linking issue. Harald Dunkel
- Re: mkinitrd linking issue. Chris Wakefield
- Re: mkinitrd linking issue. Harald Dunkel
- Re: mkinitrd linking issue. Chris Wakefield
- Re: mkinitrd linking issue. Harald Dunkel
- Re: mkinitrd linking issue. Chris Wakefield