Re: [leaf-devel] Develop Bering-uClibc package

[Martin Hejl]

Ondrej Sokol wrote:
could anybody recommend me the easiest way how-to create bering uClibc
package? 
Just any package, or a specific one?

I think about buildpacket, but I can't create working environment
for package building.
buildpacket will only work with sources created with buildtool - so it's 
always only the second step in the process.

I can't build whole Bering-uClibc 2.1.I've got latest cvs snapshot of
buildtool,sucessfuly built buildenv, but
I can't build other packages like busybox, e2fstools, nasm, etc..
busybox, sed, watchdog, netkit-base, cron and a few others are "work in 
progress" - they build on my build-environment, but that's about as much 
testing as they've got so far.
Just to get the terminology right - none of busybox, e2fstools or nasm 
is actually a _package_ - they are "sources", either needed to actually 
build some other source/package (like syslinux, which requires nasm to 
even build), or that produce binaries which are used in packages (like 
sed or busybox, which are used in root). It may sound like I'm splitting 
hair here, but it's important to get the terminology right (especially 
when troubleshooting).

For example I've built sed program which is dynamically linked with
uClibc. It is in staging/bin directory. If I execute this file I get a
error: -bash: ./sed: No such file or directory. This means sed is linked
againstuClibc library. i386-uclibc-ldd sed
works, it outputslibc.so.0 => /buildtool/staging/lib/libc.so.0 (0x00000000)
   /lib/ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0x00000000)
The second line looks strange to me. Here's what I get on my box:

$ ./i386-uclibc-ldd ./sed
        libc.so.0 => 
/devel/src/bering-uclibc/buildtool/staging/lib/libc.so.0 (0x40006000)
        ld-uClibc.so.0 => 
/devel/src/bering-uclibc/buildtool/staging/lib/ld-uClibc.so.0 (0x40000000)

$ ./sed --version
GNU sed version 2.05
The buildtool.pl uses this program while configure nasm package.
Works here. Could it be that /lib/ld-uClibc.so.0 isn't actually a link 
pointing to  /whatever/buildtool/staging/lib/ld-uClibc.so.0 ? This is 
the only explanation I'd have for strange linker problems like that.

Other than that, I'm at a loss.

Martin



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel