On Mon, Jan 5, 2015 at 1:22 PM, Cyd Haselton <chaselton@xxxxxxxxx> wrote: > On Mon, Jan 5, 2015 at 11:01 AM, Andrew Haley <aph@xxxxxxxxxx> wrote: >> On 01/05/2015 04:13 PM, Cyd Haselton wrote: >>> I'm guessing because I haven't received a reply yet but here's the >>> first few lines of 'cat gcc/nm' run in both the 4.8 and 4.9 build dirs >> >> I don't know what answer you're waiting for. >> > > This one: > >> You need to look inside the files with "nm" or something similar. >> > > In the gcc build directories? > > But now I see you meant 'examine obj files with nm' which I did. No > dlopen in any of the linked object files in both build dirs >> >> You have the command which failed on 4.9. On 4.8 it begins >> >> /bld/gcc/builddir-4.8/./gcc/xgcc -B/bld/gcc/builddir-4.8/./gcc/ >> -B/usr/gcc-4.8.4/arm-linux-androideabi/bin/ >> -B/usr/gcc-4.8.4/arm-linux-androideabi/lib/... >> >> If you run that command with the additional argument "-Wl,-Map,mapfile" >> you'll get a link map (called "mapfile") which should tell you where >> dlopen is linked from. >> >> Andrew. >> > Neither -Wl,-Map,mapfile, -Wl,-Map mapfile or -Wl,-Map=mapfile > generates said link map Update: The link map isn't generated in the 4.9 build dir because...I suspect...of the original error. The link map IS generated in the 4.8 build dir, but grep "dlopen" mapfile yields zero results. I'm running make clean && make to see if more helpfulndata is generated
