This is the mail archive of the
mailing list for the GCC project.
Re: Long paths with ../../../../ throughout
- From: Jon Grant <jg at jguk dot org>
- To: Ian Lance Taylor <iant at google dot com>
- Cc: gcc at gnu dot org
- Date: Sat, 2 Jul 2011 23:03:59 +0100
- Subject: Re: Long paths with ../../../../ throughout
- References: <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <4B68A953.firstname.lastname@example.org> <email@example.com>
On 2 February 2010 22:47, Ian Lance Taylor <firstname.lastname@example.org> wrote:
> Jon <email@example.com> 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.
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
Best regards, Jon