This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
- From: Andrew Haley <aph at redhat dot com>
- To: Cyd Haselton <chaselton at gmail dot com>
- Cc: "gcc-help at gcc dot gnu dot org" <gcc-help at gcc dot gnu dot org>
- Date: Tue, 06 Jan 2015 17:17:53 +0000
- Subject: Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
- Authentication-results: sourceware.org; auth=none
- References: <CAHu5PrboyVq7orESm4N3m+2aQZaQNPAkcG4AJ7rFnFu+Q=tKWQ at mail dot gmail dot com> <54A67520 dot 6030801 at redhat dot com> <CAHu5PrZpsNYawNMacyuZMb9owEsRFf8NN6KqsZZ-zbxYf8_JrA at mail dot gmail dot com> <54A68729 dot 6080004 at redhat dot com> <CAHu5Prav-nfzfHPoKJvJgy2VDFgFJmeJur-60hO9vGrtFgeCTA at mail dot gmail dot com> <CAHu5Prag8XZ56iyGnnhy_NPO6FC_07jV76vmeqcHMc0n7kDNuA at mail dot gmail dot com> <54AA5ED4 dot 7010700 at redhat dot com> <CAHu5PraFq7odtgFsPg5wL-ESeUd9M0x9iErj0Ywd8UpvsQw=pw at mail dot gmail dot com> <54AA719A dot 3090905 at redhat dot com> <CAHu5PraQcZU=TBScUREu-uHZQHj8GUQJUQurPxeN4YbZa7-png at mail dot gmail dot com> <54AAC367 dot 8000008 at redhat dot com> <CAHu5Pra45xnUMstM0PLvHZNj2J13OBKcvaaG_CdTGj1DB-0uOA at mail dot gmail dot com> <CAHu5PrZDkb5ixJW8abXi9+uKLsdbt8onwJjirKAJqAU_am9X+A at mail dot gmail dot com> <CAHu5PrYx+KX0Yg4hFt50YJ=c+NgHFgjVDhMC9n0k1hoqRa3WDA at mail dot gmail dot com> <54ABAC12 dot 3050100 at redhat dot com> <CAHu5Prah39c32BpxdzfKhMDY78qeMhCE=U78J0hkCETd1Kwo3Q at mail dot gmail dot com> <CAHu5PrbJxu4=W8q7_QriYhGbAiSPWth70jLXxcRZCpuXOQMQXg at mail dot gmail dot com>
On 01/06/2015 04:11 PM, Cyd Haselton wrote:
> On Tue, Jan 6, 2015 at 9:11 AM, Cyd Haselton <chaselton@gmail.com> wrote:
>> On Tue, Jan 6, 2015 at 3:34 AM, Andrew Haley <aph@redhat.com> wrote:
>
> FYI, Brian suggested an answer to the above question:
>
>> I'd start with
>
>> nm *.o |grep dlopen
>
> I've run
>
> grep -r dlopen .
>
> and Brian's command (just for kicks) and none of the libgcc input
> files in either the 4.9 or 4.8 build directories contains a call to
> dlopen.
One of the input files does, because otherwise the link would not have
failed. Maybe the input file is some internally-generated gcc magic
which does not appear on the command line, but when the link fails
there should be some info in the error message. You can run the link
command with "-v" to see what is really happening.
Andrew.