[uClibc] buildroot and other questions

Szekely Gyorgy hoditohod at csodalatos.muszaki.info
Mon Mar 28 21:30:19 UTC 2005


a bit lame, sorry:

Hi,
I'm not sure this is the right place to write, but here I go.

I wrote package support files (Config.in, whatever.mk) for alsa-lib and 
alsa-utils. When compiling alsa utils I had to set the linker flags in 
alsa-utils.mk to contain the rootfs lib-dirs:
LDFLAGS="-L$(TARGET_DIR)/lib -L$(TARGET_DIR)/usr/lib"
Why this isn't default? I mean when compiling an application that 
depends on a library of the target system, the compiler must know where 
this library is.

I'm planning to write more makefiles for the ogg packages, other command 
line audio applications. Some of these might be useful for others and I 
would be happy to contribute to this project. Is there any policy 
describing which packages can be included?

Floating points.
I'm using a PXA255 processor in a project, no FPU. I compiled the NWFPE 
in the kernel, but I've read somewhere that this is slow because the 
processor generates an exception at every FP instruction. If gcc 
compiles calls to the floating point functions directly is a bit faster. 
I enabled the "Use software floating point by default" in Toolchain 
options, and selected "libfloat" in packages, but there's no libfloat in 
the target filesystem. Actually libfloat isn't even downloaded. Why? Can 
someone please expalin me how this works?
Details:
buildroot: 200503017
Processor: Intel PXA255
Questions when running make: XScale target(10), Little-endian, has MMU

What's multilib? Do I need it? (same project)
What's armeb?


Thanks,
	George

ps: sorry for my English



More information about the uClibc mailing list