On 01/06/2015 04:11 PM, Cyd Haselton wrote: > On Tue, Jan 6, 2015 at 9:11 AM, Cyd Haselton <chaselton@xxxxxxxxx> wrote: >> On Tue, Jan 6, 2015 at 3:34 AM, Andrew Haley <aph@xxxxxxxxxx> 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.
