glibc side-by-side with Bionic

754 views
Skip to first unread message

Karim Yaghmour

unread,
Feb 18, 2012, 10:47:49 PM2/18/12
to android-platform

I've just created a Cyborgstack branch that contains a glibc-based stack
sitting side-by-side with Bionic:
$ repo init -u git://github.com/cyborgstack/android.git -b glibc
$ repo sync
$ ...

Note that this does NOT replace Bionic with glibc. Instead, we just use
the /bin/ and /lib/ directories which aren't being used by Android to
host a glibc-based stack. The BusyBox included, for instance, is linked
against glibc.

As always, feedback welcomed.

--
Karim Yaghmour
CEO - Opersys inc. / www.opersys.com
http://twitter.com/karimyaghmour

Nathaniel Husted

unread,
Feb 18, 2012, 10:54:52 PM2/18/12
to android-...@googlegroups.com
Have you had any success, or have attempted, a full replacement of
bionic with something that is glibc compatible (either glibc, uclibc,
eglibc)? It's an idea I've had for a project for about a year now
(since I attempted to port some GNU/*nix stuff and noticed how much
bionic is missing) but never found time to do.

Cheers,
Nathaniel

> --
> 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.
>

Karim Yaghmour

unread,
Feb 19, 2012, 7:35:07 PM2/19/12
to android-...@googlegroups.com, Nathaniel Husted

I've personally never tried it myself. I've come across at least one
person who did do that as part of a project in their company, but I
can't talk about that ;) ... nor do I have the code. I've been told it
isn't "that" complicated.

If you ever do that, I'd be more than happy to include it as an option
in Cyborgstack. Currently I'm hosting every "major" feature as a
separate branch, but I'm planning to merge it all into a single branch
as soon as I can find a satisfactory configuration system for it all.

Currently the most obvious option would be the kernel's Kconfig, but I
suspect it's tightly tied to the use of recursive build systems (which
the AOSP isn't using.) And the AOSP's "CAPITALIZED_FEATURE_FLAGS=foo"
method is ok if and only if you know ahead of time the entire feature
list, which isn't going to be the case with something like Cyborgstack.

--
Karim Yaghmour
CEO - Opersys inc. / www.opersys.com
http://twitter.com/karimyaghmour

Karim Yaghmour

unread,
Feb 19, 2012, 7:39:00 PM2/19/12
to android-...@googlegroups.com, Nathaniel Husted

And, FWIW, I did have a handful of individuals independently come up to
me as part of last week's Android Builders Summit and inquire about
exactly what you're inquiring about ...

--
Karim Yaghmour
CEO - Opersys inc. / www.opersys.com
http://twitter.com/karimyaghmour

Nathaniel Husted

unread,
Feb 19, 2012, 8:02:39 PM2/19/12
to Karim Yaghmour, android-...@googlegroups.com
I'm glad to see it's a very popular idea. This summer I will hopefully
have time to do some of this work as my normal academic duties will be
on hold for a few months. I'd certainly make the modifications
publicly available under the GPL. If I'm really lucky, one of these
many folks you mention have showed interest will get to it before I
do. :-)

Cheers,
Nathaniel


On Sun, Feb 19, 2012 at 7:39 PM, Karim Yaghmour

Reply all
Reply to author
Forward
0 new messages