Re: [leaf-wisp] Binaries in source tree

Vladimir Ivaschenko wrote:
> 
> Binaries are there because I didn't have time to make scripts for 
> building from source and nobody else volunteered.
> 
> They shouldn't cause any problem, as these binaries are only used inside 
> WISP-Dist. They are not executed during image build process.

I know. Build process finished everytime without any error, but I got 
errors during every boot :-( Some problems was fixed by replays I found 
in list.

The last problem was, that I stopped here (compiled od Debian Woody with 
gcc 3.0)

******************** Debian compilation ***************************
Generating POSIXness links...
Generating tinylogin links...
chown and chmod /dev...
unmounting /var/lib/lrpkg/mnt
unmounting /mnt1
removing /mnt1
echo: /lib/libc.so.6: version `GCC_3.0' not found (required by echo)
INIT: version 2.78 booting
INIT: No inittab file found

Enter runlevel:
********************************************************************


than I tried install RedHat 9, compiled and stopped here



************************** RH compilation **************************
Installation finished.
Generating POSIXness links...
Generating tinylogin links...
chown and chmod /dev...
unmounting /var/lib/lrpkg/mnt
unmounting /mnt1
removing /mnt1
echo: /lib/libc.so.6: version `GLIBC_2.3' not found (required by echo)
INIT: version 2.78 booting
INIT: No inittab file found

Enter runlevel:
*********************************************************************

Problem occures when 'linuxrc' executes line
'qt ln -s -f /bin/busybox.dyn /bin/busybox'
ie. links precompiled binary of 'busybox.dyn'

What now?

Patrick



-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click