Hi all.
At least I've got semi-working buildenv with fresh GCC. It seems that 
some packages will become broken  - like netkit-base (I removed it at 
all & enabled inetd in busybox) & possible some others. Now I can't say 
how much packets will be broken - I used wrong system name at GCC 
assembling (i386-pc-linux-gnu will cause usage of 'sincos' function that 
isn't supported by uClibc, so I changed platform name to 
i686-pc-linux-uclibc), but it seems that most packages will be built OK 
- now, with non-proper system name, there are not too much broken 
packages - ncurses with related packages & some other - up to 10-15 
additional packages.
Now I run recompilation from scratch, and tomorrow I'll look at results.
Also I noticed that something erased /dev/null device & replaced it by 
file - possible it was just a non-repeatable bug...


------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev

_______________________________________________
leaf-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to