Yea. I'm trying to smush this into a build process. The Ruby build process believes it knows how to set the internal libpath of the executables but it actually does not. It does not know what gcc knows and the end result is an executable that can not find libgmp.a. I was hoping to teach it Ruby's build process to construct a better libpath.
The only thought I have is to compile a simple executable and then pull the libpath in the executable out of that using dump -H but I was hoping for something simpler. Thank you for your time, Perry On Jan 25, 2014, at 6:39 AM, Jonathan Wakely <jwakely....@gmail.com> wrote: > On Jan 25, 2014 1:32 AM, "Perry Smith" wrote: >> >> I think, a %D in a spec creates a list of -L/a/b/c -L/d/e/f. gcc -dumpspecs >> shows me that link_libgcc goes to %D but it does not show me what %D >> produces. Is there a way to get gcc to dump that out? >> >> Basically what I'm trying to do is find the list of library paths that GCC >> tells ld to use when it calls ld. > > Adding -v to the gcc command will show everything it passes to the > linker, you should be able to deduce what comes from the specs from > that.
signature.asc
Description: Message signed with OpenPGP using GPGMail
