[uClibc]PaX and uClibc, more tests

[Thomas Cameron]

Peter,
	Have you solved the problem yet?  If not, here are a few suggestions.  First 
off, if all busybox programs are working properly, and all others are not, 
check your busybox configuration.  When you built it, you may have built it 
so that busybox applets always win.  This basically means that your shell 
(which is a symlink to busybox) thinks that all programs you call are 
internal to it.  Essentially, this would be like calling a "feature" of the 
bash shell, instead of an external program.
	One other thing to check is how ./configure happened to configure each 
additional program.  By default, running ./configure will _not_ set up 
programs to compile against uClibc.  Additionally, there are known library 
leaks when using the compiler wrapper that is built by uClibc.  You'd have to 
ask Erik more about this, though, as I'm not a uClibc developer.
	I do know, however, that I use buildroot to circumvent any compiling issues I 
may have with certain packages.  Many packages' configuration and/or make 
scripts are _badly_ broken, and will NOT allow you to compile against a 
non-glibc library.  When using a buildroot system, you simply `chroot` into 
your buildroot environment, and configure/compile as usual.  There are 
updates and additions to buildroot happening CONSTANTLY, so it is best to 
check out the latest from the cvs repository.  To do this, simply type the 
following (assuming you have already executed the cvs login command):

cvs -z3 -d:pserver:anonymous at uclibc.org:/var/cvs co buildroot

	This will grab the latest copy, and place a `buildroot` directory in your 
current directory.

	Anyway, enough from me. Good luck!

Sincerely,
Thomas Cameron
CEI Systems, Inc.


On Monday 13 January 2003 09:42 am, Peter S. Mazinger wrote:
> Hello!
>
> I have made following tests after the previously sent mail related to PaX:
> downloaded i386 iso image (as of 2003.01.12) and tried to boot it.
> PaX EMUTRAMP option was disabled for the used kernel.
> kernel is booting, (probably because it is using busybox's init, I have
> used SysVinit, that won't work)
> bash can't be executed, and probably all non-busybox utilities built
> against uClibc (I tried to run ./configure to build from source).
> It looks like busybox does not have the problem, but "foreign" programs
> do.
>
> Peter