[BL] uclibc static lynx 2.8.6dev16, lynx.lss and mplayer
keesan at sdf.lonestar.org
Fri Jan 20 19:58:48 EST 2006
On Fri, 20 Jan 2006, David Moberg wrote:
> sindi keesan wrote:
>> I looked through a lot of old emails. Do you mind if I link your BL
>> download site to my site? I know you have a varying set of files there.
> I don't mind; that's what URLs are made for.
I have to go find it again now...
>> So this 21MB image gets mounted to loop and then copied to a large
>> directory (or another partition) and includes uclibc library, gcc,
>> binutils, bash, and busybox. I presume after copying it to that directory
>> I also copy the source code to that directory before I chroot there and
>> then compile it and it ignores any other libc on the computer.
>> Want to bet on it? I will also need to either find precompiled, or
>> compile from source code, various dependencies such as ncurses, or
>> libjpeg, etc., or use ones compiled statically with glibc which I think
>> would make them larger. Where do I find precompiled libraries?
> You'll have to compile them yourself. Or try some from the uClibc
> port of Debian. The good news is that uClibc comes with curses
Does uclibc Debian already have a lot of libraries and other programs
compiled dynamically against uclibc?
> already, so you can start building links or lynx right away. X might
> be a little trickier. I've found that there is just a handful of libraries
> that are used by the various source code.
I don't plan to compile X, if that is what you meant.
Could I compile dynamically against uclibc and add uclibc to the regular
library partition(s)? It might work with some programs that won't compile
because glibc 2.1.3 or 2.2.5 are too old.
I left my other computer turned on downloading root_fs at about 4K/sec
(only 1 hr 20 min estimated arrival time).
>> I hope the instructions tell you how to compile statically or dynamically.
> I compile the app. normally, and then I start X and chroot in from
> an rxvt. Then remove the compiled application (before installation)
> and run make again. Make will just go in and out of several
> directories, then it will execute one command to rebuild the
> deleted binary. Use X to copy and paste the command, then
> add the '-static' command to rebuild it statically. Make sure
> that you are in the right directory.
Are you saying I need to use X in order to compile statically?
> You can also usually do
> LDFLAGS="-static" ./configure
> or make LDFLAGS="-static" to do the same thing. There is
> one notable exception: binutils, which requires "-all-static".
This would be static against uclibc, libncurses, etc.?
Can I make it static against uclibc but dynamic against other libraries
which I already have on my computer?
> There is a learning curve, but it's a much easier one than
> trying to get odd pieces of hardware like winmodems to
> work with BL.
I was impressed with your lucent modem victory.
But have never run across a 56K lucent winmodem. There are piles of
56K ISA and PCI winmodems around for $1.
More information about the BasLinux