Marin, > > Ondrej Sokol wrote: >> could anybody recommend me the easiest way how-to create bering uClibc >> package? > Just any package, or a specific one?
I have a small program which I want to integrate into LEAF and boot everything from CF card. I would like to create a lrp package. The program is one binary file + configuration file + start script. I would like to run it under non root user. I guess it will be very simple package. I can compile my program against uClibc but I don't know what else I need to put into lrp package in what directory structure.Could you recommend me any (up to date) document or package which I can use as an example? >> 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. OK, so buildtool creates binary package sources - this is the first step and buildpacket crates lrp packages - this is the second step. >> 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. Yes, that was the problem exactly. I didn't have the link from /lib/ld-uClibc.so.0 to /whatever/buildtool/staging/lib/ld-uClibc.so.0. Now I know why you have this notice in your Development guide, I didn't noticed it before :-) I've found another problem: when I execute ./buildtool.pl describe I get the following: The following packages and sources are available: Sources: --------------------------------------------------------- util-linux fdisk and mkfs.minix net-tools net-tools hostap HostAP libgmp Multiprecision arithmetic library ncurses Ncurses libs linux kernel source only package sysvinit sysvinit sed sed e2fsprogs The EXT2 file system utilities and libraries. nasm Netwide Assembler hdparm Tune hard disk parameters for high performance dosfstools provides mkfs.dos automake Up to date automake for the buildenv flex flex nttcp TCP benchmarking utitily tcp_wrappers Wietse Venema's TCP wrappers library e3 e3 editor libpcap user-level packet capture zlib zLib shared libraries syslinux Syslinux boot-loader busybox busybox libtool Up to date libtool for the buildenv ash ash bison bison kgcc gcc 2.95 for compiling kernels autoconf Up to date autoconf for the buildenv Packages: --------------------------------------------------------- openvpn VPN daemon lrpstat lrpStat is a java-applet/application that displays information about network devices on a linux routerbuildenv this holds everything to build cross build env lcd4linux LCD support for LEAF lzo Online compression library Argument "dmalloc" isn't numeric in exists at buildtool/Config.pm line 181. Bad index while coercing array into hash at buildtool/Config.pm line 181. dmalloc And another question, you added to README file : Requirements: ============= ... fakeroot (you can find it in the tools directory) What do you mean ? I can't find fakeroot in the buildtool/tools directory. Fakeroot is Debian package, do you mean the same thing, where do you use it? Thanks for your help very much Ondrej ------------------------------------------------------- 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
