This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Long paths with ../../../../ throughout
- From: Ian Lance Taylor <iant at google dot com>
- To: Jon Grant <jg at jguk dot org>
- Cc: gcc at gcc dot gnu dot org
- Date: Sat, 02 Jul 2011 21:27:06 -0700
- Subject: Re: Long paths with ../../../../ throughout
- References: <19ac3f7a1001190934q65b08a02q37f487bd735311c3@mail.gmail.com> <mcr636ym009.fsf@dhcp-172-17-9-151.mtv.corp.google.com> <19ac3f7a1001230826l5006ae86re2850bb3bbcfb629@mail.gmail.com> <mcrbpgivybr.fsf@dhcp-172-17-9-151.mtv.corp.google.com> <4B68A953.4090107@jguk.org> <mcr1vh31cib.fsf@dhcp-172-17-9-151.mtv.corp.google.com> <CAGc9EvcQJ6AmM1xm0DNwp-fWkCrndyfsH+Bh8Z36pO3o0+Ns2w@mail.gmail.com>
Jon Grant <jg@jguk.org> writes:
> On 2 February 2010 22:47, Ian Lance Taylor <iant@google.com> wrote:
>> Jon <jg@jguk.org> writes:
>>
>>> Is there a way to get collect2 to save the temporary .c file it
>>> generates to have a look at it? I believe it may be the __main()
>>> function, with the -debug option it gives the attached
>>> gplusplus_collect2_log.txt, looking at the [/tmp/ccyBAI9V.c] file
>>> though it is empty, any ideas?
>>
>> Using -debug will direct collect2 to save the temporary .c file when
>> it creates one. ÂHowever, in ordinary use on GNU/Linux, collect2 will
>> never generate a temporary .c file.
>
> Hello Ian,
>
> Another reply for this old thread. I wondered, if collect2 is
> possibly not needed in normal use on GNU/Linux, could GCC be
> configured to call ld directly in those cases to save launching
> another binary.
collect2 is needed if you use -frepo or -flto.
Ian