Can GNU libc coexist with bionic in the same userspace?
Has anyone tried? And failed or succeeded?
--
You received this message because you are subscribed to the Google Groups "android-platform" group.
To post to this group, send email to android-...@googlegroups.com.
To unsubscribe from this group, send email to android-platfo...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-platform?hl=en.
Can GNU libc coexist with bionic in the same userspace?
Has anyone tried? And failed or succeeded?
On Wed, Mar 23, 2011 at 3:57 PM, JAlexoid (Aleksandr Panzin) <jale...@gmail.com> wrote:
Can GNU libc coexist with bionic in the same userspace?
Has anyone tried? And failed or succeeded?
Nope, they will conflict on many front. For example, each malloc() implementation thinks it is handling sbrk() exclusively so expect some weird memory corruption issues.Also, plenty of other stuff regarding threads, standard file descriptors, errno, the dynamic linker and others will simply not work correctly.
Hi,
The answer is yes and no.
1. Its not possible if the executables linked to BIONIC and GLIBC are expected to coexist in the same root file system unless the GLIBC ones are statically linked.
2. Its possible if there are 2 root file systems (one is BIONIC specific and the other is GLIBC specific) with "chroot" from one root-fs to the other.
Warm Regards,
Anil
On Wed, Mar 23, 2011 at 8:27 PM, JAlexoid (Aleksandr Panzin) <jale...@gmail.com> wrote:
Can GNU libc coexist with bionic in the same userspace?
Has anyone tried? And failed or succeeded?
--
You received this message because you are subscribed to the Google Groups "android-platform" group.
To post to this group, send email to android-platform@googlegroups.com.
To unsubscribe from this group, send email to android-platform+unsubscribe@googlegroups.com.