[BL] compiling with uclibc
keesan at sdf.lonestar.org
Tue Jan 24 21:22:56 EST 2006
On Tue, 24 Jan 2006, David Moberg wrote:
> sindi keesan wrote:
>> Anyway, despite scsi problems and framebuffer use, I was able, with 2.4.31
>> kernel, to chroot to /uclibc and the prompt is now:
>> [root at BasicLinux /]#
>> ls shows color and puts / after directories (unlike the BL2 ls)
>> Is it worth trying to compile ndiswrapper with uclibc?
> No, the majority of it is kernel modules which are library-independent.
>> It did not work with gcc 2.95.3 - which version did not work for you?
> I tried to build the latest version of ndiswrapper with gcc 2.95.3. But
> I think the actual problem is with make, so I will upgrade that and
> try again.
One of my problems was trying to compile after booting with 2.4.31 because
I only have 2.2.16 kernel source code. uclibc does not seem to have
kernel source code.
>> I tried to compile fbutils and was told I don't have bison. I do have
>> flex, which it also needs.
>> Then I tried to compile e3 but I need nasm.
>> Are these available precompiled for uclibc?
> Probably not. But they don't take very long to compile, and you
> should only need to ./configure and make.
Assuming they compile. So far nothing has compiled.
>> I think I had compiled this in BL2 by editing out asfxload and alsa lines
>> in Makefile.in and copying to Makefile. libasound is I think alsa.
>> So I tried to edit Makefile.in but there is no pico or e3pi.
>> I found vi.
> BL3 e3pi is static so you can copy that into the uClibc root and
> use it.
I realized that later.
>> To insert text type i first, to give commands type ESC,
>> to exit without saving in command mode type :q! or to save :wq
>> To search for also ESC /alsa.
> To delete the current line, hold Shift and press D. This is handy
> when you need to delete a lot of text at once.
> I save by holding Shift and pressing Z twice, didn't know about
I got stuck in the editing process so opened another terminal and searched
on vi and manual and found a detailed introduction. One of the first
things they taught was how to exit with and without saving. They also
suggested ESC ZZ, I think.
>> If I run 'make' I get a lot of undefined references to 'pow' and 'log' but
>> it did get partway through compilation and I have an sfxload.o now.
>> This had compiled with gcc 2.95.3 or maybe it was egcs. I think I just
>> edited Makefile.in and did not configure at all.
> Unlike glibc, uClibc has pow and log in libm instead of libc. It appears
> that awesfx assumes that is is being used with glibc (and pilot-link
> also appears to make the same assumption). Try this:
Why does uClibc not organize itself like glibc so that programs can be
compiled more easily?
> LDFLAGS="-lm" ./configure
lm meaning libm?
> Then remake. Or edit the Makefile(s) and add -lm to the LDFLAGS
> or LIBS line.
I will try this. What does LDFLAGS mean? Is it pointing ld-linux to
My main reason for compiling with uClibc would be so that I can compile
programs requiring later libc, without having to download and install the
later libc. Is this likely to be possible once I get past this sort of
stumbling block? I should read up on how to use uClibc at their site.
More information about the BasLinux