Re: Trouble building gcc on debian testing

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Anyway:

/usr/lib/x86_64-linux-gnu/crt1.o  Can't be found but

/usr/lib/x86_64-linux-gnu  is in ld.so.conf


...

Regards.

Pedro

On Fri, Jul 8, 2011 at 2:30 PM, Pedro Larroy
<pedro.larroy.lists@xxxxxxxxx> wrote:
> Hi
>
> In which reference platform is it known to build without so much hassle?
>
>
> Here is the configure error:
>
> configure:3635: /home/piotr/devel/gcc_obj/./gcc/xgcc
> -B/home/piotr/devel/gcc_obj/./gcc/
> -B/usr/local/x86_64-unknown-linux-gnu/bin/
> -B/usr/local/x86_64-unknown-linux-gnu/lib/ -isystem
> /usr/local/x86_64-unknown-linux-gnu/include -isystem
> /usr/local/x86_64-unknown-linux-gnu/sys-include    --version >&5
> xgcc (GCC) 4.7.0 20110708 (experimental)
> Copyright (C) 2011 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> configure:3646: $? = 0
> configure:3635: /home/piotr/devel/gcc_obj/./gcc/xgcc
> -B/home/piotr/devel/gcc_obj/./gcc/
> -B/usr/local/x86_64-unknown-linux-gnu/bin/
> -B/usr/local/x86_64-unknown-linux-gnu/lib/ -isystem
> /usr/local/x86_64-unknown-linux-gnu/include -isystem
> /usr/local/x86_64-unknown-linux-gnu/sys-include    -v >&5
> Reading specs from /home/piotr/devel/gcc_obj/./gcc/specs
> COLLECT_GCC=/home/piotr/devel/gcc_obj/./gcc/xgcc
> COLLECT_LTO_WRAPPER=/home/piotr/devel/gcc_obj/./gcc/lto-wrapper
> Target: x86_64-unknown-linux-gnu
> Configured with: ../gcc/configure
> Thread model: posix
> gcc version 4.7.0 20110708 (experimental) (GCC)
> configure:3646: $? = 0
> configure:3635: /home/piotr/devel/gcc_obj/./gcc/xgcc
> -B/home/piotr/devel/gcc_obj/./gcc/
> -B/usr/local/x86_64-unknown-linux-gnu/bin/
> -B/usr/local/x86_64-unknown-linux-gnu/lib/ -isystem
> /usr/local/x86_64-unknown-linux-gnu/include -isystem
> /usr/local/x86_64-unknown-linux-gnu/sys-include    -V >&5
> xgcc: error: unrecognized command line option '-V'
> xgcc: fatal error: no input files
> compilation terminated.
> configure:3646: $? = 1
> configure:3635: /home/piotr/devel/gcc_obj/./gcc/xgcc
> -B/home/piotr/devel/gcc_obj/./gcc/
> -B/usr/local/x86_64-unknown-linux-gnu/bin/
> -B/usr/local/x86_64-unknown-linux-gnu/lib/ -isystem
> /usr/local/x86_64-unknown-linux-gnu/include -isystem
> /usr/local/x86_64-unknown-linux-gnu/sys-include    -qversion >&5
> xgcc: error: unrecognized command line option '-qversion'
> xgcc: fatal error: no input files
> compilation terminated.
> configure:3646: $? = 1
> configure:3666: checking for C compiler default output file name
> configure:3688: /home/piotr/devel/gcc_obj/./gcc/xgcc
> -B/home/piotr/devel/gcc_obj/./gcc/
> -B/usr/local/x86_64-unknown-linux-gnu/bin/
> -B/usr/local/x86_64-unknown-linux-gnu/lib/ -isystem
> /usr/local/x86_64-unknown-linux-gnu/include -isystem
> /usr/local/x86_64-unknown-linux-gnu/sys-include    -g -O2   conftest.c
>  >&5
> /usr/bin/ld: cannot find crt1.o: No such file or directory
> /usr/bin/ld: cannot find crti.o: No such file or directory
> collect2: error: ld returned 1 exit status
> configure:3692: $? = 1
> configure:3729: result:
> configure: failed program was:
> | /* confdefs.h */
> | #define PACKAGE_NAME "GNU OpenMP Runtime Library"
> | #define PACKAGE_TARNAME "libgomp"
> | #define PACKAGE_VERSION "1.0"
> | #define PACKAGE_STRING "GNU OpenMP Runtime Library 1.0"
> | #define PACKAGE_BUGREPORT ""
> | #define PACKAGE_URL "http://www.gnu.org/software/libgomp/";
> | #define PACKAGE "libgomp"
> | #define VERSION "1.0"
> | /* end confdefs.h.  */
> |
> | int
> | main ()
> | {
> |
> |   ;
> |   return 0;
> | }
> configure:3735: error: in
> `/home/piotr/devel/gcc_obj/x86_64-unknown-linux-gnu/libgomp':
> configure:3739: error: C compiler cannot create executables
> See `config.log' for more details.
>
>
> On Fri, Jul 8, 2011 at 2:08 PM, Jonathan Wakely <jwakely.gcc@xxxxxxxxx> wrote:
>> On 8 July 2011 11:27, Pedro Larroy wrote:
>>> Hi
>>>
>>> I'm trying to build gcc from svn on debian testing, I manually solved
>>> a couple of obstacles like crti.o and crtn.o not being found. By cp
>>> /usr/lib/x86_64-linux-gnu/crti.o x86_64-unknown-linux-gnu/libgcc/
>>>
>>> In which location are they expected?
>>
>> Not where Debian puts them.
>>
>>>  Now I'm stuck with the following error:
>>>
>>> checking for x86_64-unknown-linux-gnu-gcc...
>>> /home/piotr/devel/gcc_obj/./gcc/xgcc
>>> -B/home/piotr/devel/gcc_obj/./gcc/
>>> -B/usr/local/x86_64-unknown-linux-gnu/bin/
>>> -B/usr/local/x86_64-unknown-linux-gnu/lib/ -isystem
>>> /usr/local/x86_64-unknown-linux-gnu/include -isystem
>>> /usr/local/x86_64-unknown-linux-gnu/sys-include
>>> checking for C compiler default output file name...
>>> configure: error: in
>>> `/home/piotr/devel/gcc_obj/x86_64-unknown-linux-gnu/libgomp':
>>> configure: error: C compiler cannot create executables
>>> See `config.log' for more details.
>>> make[2]: *** [configure-stage1-target-libgomp] Error 77
>>> make[2]: Leaving directory `/home/piotr/devel/gcc_obj'
>>> make[1]: *** [stage1-bubble] Error 2
>>> make[1]: Leaving directory `/home/piotr/devel/gcc_ob
>>>
>>>
>>> Any clues?
>>
>> It tells you right there what to do. See config.log for more details
>> (the one it's referring to is
>> x86_64-unknown-linux-gnu/libgomp/config.log)
>>
>



[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux