This is the mail archive of the
mailing list for the GCC project.
Re: Android native build of GCC
- From: Richard Biener <richard dot guenther at gmail dot com>
- To: Andrew Haley <aph at redhat dot com>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>, Cyd Haselton <chaselton at gmail dot com>
- Date: Fri, 9 Jan 2015 13:30:20 +0100
- Subject: Re: Android native build of GCC
- Authentication-results: sourceware.org; auth=none
- References: <54AE581C dot 5070003 at redhat dot com> <CAFiYyc0FGy3G9hJR5bM0YsKHcBAyHjdznXeioOfCkuEU1KjR_A at mail dot gmail dot com> <54AFC695 dot 8010200 at redhat dot com>
On Fri, Jan 9, 2015 at 1:16 PM, Andrew Haley <firstname.lastname@example.org> wrote:
> On 01/09/2015 10:33 AM, Richard Biener wrote:
>> On Thu, Jan 8, 2015 at 11:12 AM, Andrew Haley <email@example.com> wrote:
>>> Android native GCC can't support LTO because of a lack of support for
>>> dlopen() in the C library. How should we patch the configury to disable
>>> LTO by default?
>> How does LTO need dlopen? It seems it only cannot use the linker
> That's right, it's the plugin which is causing the problem.
Building it, I suppose? Does --disable-lto-plugin work?
>> in which case the existing check for plugin-supporting ld should
>> catch it?
> It doesn't seem to. The problem is probably caused by
> libfakechroot.so, which intercepts calls to dlopen() and tries to
> forward them. Unfortunately dlopen() is not in Android's libc, so
> libfakechroot returns a link error for dlopen(). I don't know what
> the check for plugin-supporting ld does, but I guess it doesn't call
> I'll grant you that this isn't really our bug: libfakechroot shouldn't
> be exporting dlopen() on Android.