* print out %D spec
@ 2014-01-25 12:39 Perry Smith
2014-01-25 15:26 ` Jonathan Wakely
0 siblings, 1 reply; 3+ messages in thread
From: Perry Smith @ 2014-01-25 12:39 UTC (permalink / raw)
To: gcc List
[-- Attachment #1: Type: text/plain, Size: 351 bytes --]
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.
Thank you for your time,
Perry
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: print out %D spec
2014-01-25 12:39 print out %D spec Perry Smith
@ 2014-01-25 15:26 ` Jonathan Wakely
2014-01-25 20:34 ` Perry Smith
0 siblings, 1 reply; 3+ messages in thread
From: Jonathan Wakely @ 2014-01-25 15:26 UTC (permalink / raw)
To: Perry Smith; +Cc: gcc List
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: print out %D spec
2014-01-25 15:26 ` Jonathan Wakely
@ 2014-01-25 20:34 ` Perry Smith
0 siblings, 0 replies; 3+ messages in thread
From: Perry Smith @ 2014-01-25 20:34 UTC (permalink / raw)
To: Jonathan Wakely; +Cc: gcc List
[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]
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.gcc@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.
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-01-25 16:18 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-01-25 12:39 print out %D spec Perry Smith
2014-01-25 15:26 ` Jonathan Wakely
2014-01-25 20:34 ` Perry Smith
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).