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 <jg at jguk dot org>
- Cc: gcc at gnu dot org
- Date: Tue, 02 Feb 2010 14:47:08 -0800
- 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>
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.
> checking for correct version of mpfr.h... yes
> checking for the correct version of mpc.h... no
> configure: error: Building GCC requires GMP 4.2+, MPFR 2.3.2+ and MPC
> 0.8.0+.
> Try the --with-gmp, --with-mpfr and/or --with-mpc options to specify
> their locations. Source code for these libraries can be found at
> their respective hosting sites as well as at
> ftp://gcc.gnu.org/pub/gcc/infrastructure/. See also
> http://gcc.gnu.org/install/prerequisites.html
>
> Thank you for your help so far.
Take a look at the config.log file to see the test that failed.
Ian