The Bering-uclibc developers guide is relatively up to date (if not, please point me to where its outdated).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?
For a package definition that is relatively simple, look at lcd4linux - it should have everything that you need for your package (probably a little more, like the ./configure stuff, but removing that should not be much of a problem).
Correct.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.
;-)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:Oops - you're right - dmalloc was specified twice in the config in CVS (which confused perl). Should be fixed now (just do a "cvs update" in your conf directory).
when I execute ./buildtool.pl describe I get the following: (...) 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 :_I_ didn't mean anything (I didn't write the readme, I just contributed a bit, if at all) ;-) What happened here was that the fakeroot package was removed (probably in error, but I don't know the reasoning behind removing it) from the tools directory. I re-committed it, so if you do a "cvs update" in your tools directory, you should find it.
Requirements:
=============
...
fakeroot (you can find it in the tools directory)
What do you mean ?
Correct - that's the one. If you're running debian, simply make sure you have it installed. If you're using something else (like me), then compile and install the sources. You don't _need_ to run fakeroot to build packages (fakeroot is only used in conjunction with buildpacket) - you can simply su to root (you need some kind of root privileges, otherwise the ownerships of the files in the lrp will be screwed up). But I'd strongly advise against doing anything as root, unless there is no other way.Fakeroot is Debian package, do you mean the same thing, where do you use it?
I hope that helps.
Martin
------------------------------------------------------- This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek For a limited time only, get FREE Ground shipping on all orders of $35 or more. Hurry up and shop folks, this offer expires April 30th! http://www.thinkgeek.com/freeshipping/?cpg=12297
_______________________________________________ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
