gentoobionic / bionic Goto Github PK

All files should be installed to their proper (w.r.t. DESTDIR and perfix) directories with the correct permissions.

I expect that $(INSTALL) should be used for this purpose.

change the behaviour of /sbin/linker - I want this to be more like ld-linux.so

• this means it should work as a drop-in replacement with ldd(1)
• also a rename to /lib/ld-linux.so would be awesome
• net result is that bionic's linker has the same semantics as a -gnu* toolchain

autogen.sh fails because it cannot find libgcc_shared_fake/Makefile.in

This was working. It might still work, but there are probably some kinks to be worked out.

Generally, all BUILT_SOURCES (hint, hint) should be in the build directory and not the source directory.

A completely arbitrary define (__FORCE_THUMB2) was used to hack thumb / thumb2 support. Rather than using a completely arbitrary define, use the more conventional ones, defined in

libc/arch-arm/include/machine/cpu-features.h

This is not related to #28 , but it has a similar symptom; sys/linux-syscalls.h file is also not generated when using python-3.3 (at least with Gentoo/x86). It works by setting the interpreter back to python-2.7 (e.g. eselect set python 1).

python ./libc/tools/gensyscalls.py x86 ./ libc/arch-x86/syscalls > syscalls.stamp
File "./libc/tools/gensyscalls.py", line 22
print "could not find the Bionic root directory. aborting"
...
mkdir -p libc/arch-x86/bionic/
libc/arch-x86/bionic/_exit_with_stack_teardown.S:2:32: fatal error: sys/linux-syscalls.h: No such file or directory
compilation terminated.
libc/arch-x86/bionic/clone.S:2:32: fatal error: sys/linux-syscalls.h: No such file or directory
compilation terminated.
libc/arch-x86/bionic/futex_x86.S:2:32: fatal error: sys/linux-syscalls.h: No such file or directory
compilation terminated.

modify the crt*.o files, possibly, so that we don't need an -mbionic in GCC

• rename crt*.o to be compatible with crti.o, crt1.o, crtn.o, etc
• net result is that people can use the same semantics as a -gnu* toolchain

• identify and properly compile .thumb / .arm compilation targets
• generate rules

root@minnow:/chroot/usr/lib# chroot /chroot /usr/lib/hello
Floating point exception

Possibly use http://posixtest.sourceforge.net

arch:x86

scanelf -qT libc.so | wc -l
219

most were referencing __set_errno

For source-based package managers (e.g. portage) that build code in a sandbox, writing to directories outside of the sandbox can break the build. Currently, gensyscalls.py writes to /tmp/bionic_gensyscalls/.

verify linkage entirely, using custom linker rules in Makefile.am

• see http://dev.gentoo.org/~vapier/crt.txt
• that means, I should be able to drop it in my /usr/i686-pc-linux-bionic chroot
  and it should Just Work (TM)
• specifically, when building .so's, the order of the crt*.o files must be specified for the binary to function properly

I'm not sure if it's just issue #10 that is blocking this, but as soon as that gets resolved, this needs to be verified.

All make dependencies should be validated.

This or anything later carrying the 'android-4.4*' tag.

https://android.googlesource.com/platform/bionic/+/android-4.4_r1.2

Headers should also be installed to their respective (w.r.t. DESTDIR, prefix) locations.

The kernel header should not be installed in this stage, or it should be optional. This is so that e.g. Gentoo's sys-kernel/bionic-kernel-headers still works.