[Bug libstdc++/35679] Cannot build cross compiler for i686-pc-linux-gnu: configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES

2008-03-30 Thread pinskia at gcc dot gnu dot org


--- Comment #3 from pinskia at gcc dot gnu dot org  2008-03-30 20:19 ---
Using a sysroot or setting --prefix for both the newlib build and the GCC build
is the easiest way of getting a cross build to work.

Anyways here are the options I use to build a cross build for spu:
stage1
  binutils: ../src/configure --target=spu-elf --prefix=${HOME}/gcc-spu
  gcc: --prefix=${HOME}/gcc-spu --enable-languages=c --with-mpfr=/usr/local
--with-newlib --without-headers --target=spu-elf
  newlib: ../src/configure --target=spu-elf --prefix=${HOME}/gcc-spu
stage2
  gcc: --prefix=${HOME}/gcc-spu --enable-languages=c,obj-c++
--with-mpfr=/usr/local --with-newlib --target=spu-elf --with-headers


This works without changing any source or headers too.

Thanks,
Andrew Pinski


-- 

pinskia at gcc dot gnu dot org changed:

   What|Removed |Added

   Severity|blocker |normal
 Status|UNCONFIRMED |RESOLVED
 GCC target triplet|i686-pc-linux-gnu   |i686-emc-elf
 Resolution||WORKSFORME


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35679



[Bug libstdc++/35679] Cannot build cross compiler for i686-pc-linux-gnu: configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES

2008-03-24 Thread brian at dessent dot net


--- Comment #1 from brian at dessent dot net  2008-03-24 19:54 ---
Subject: Re:   New: Cannot build cross compiler for 
 i686-pc-linux-gnu: configure: error: Link tests are not allowed after 
 GCC_NO_EXECUTABLES

yakov at emc dot com wrote:

 --target=i686-emc-elf --enable-languages=c++ --disable-multilib --with-gnu-as

Your title for this bug is misleading as it seems you're building a
cross for a newlib bare metal target, not i686-pc-linux-gnu.  That's
just the host, and is irrelevant to the issue.

There is currently a known problem with the libstdc++ configury and bare
metal newlib targets.  You can fix it either by providing BSP files
(crt*.o, linker script, etc) for your board so that test programs can be
linked, or you can disable the AC_LIBTOOL_DLOPEN check in
libstc++-v3/configure.ac for newlib targets, as in
http://gcc.gnu.org/ml/gcc/2007-11/msg00790.html.  For a summary of the
history of this issue:
http://gcc.gnu.org/ml/gcc/2008-03/msg00515.html.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35679



[Bug libstdc++/35679] Cannot build cross compiler for i686-pc-linux-gnu: configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES

2008-03-24 Thread yakov at emc dot com


--- Comment #2 from yakov at emc dot com  2008-03-24 20:29 ---
Subject: Re:  Cannot build cross compiler for i686-pc-linux-gnu:
 configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES

Brian,
first, thank you very much for such a quick response.

Actually, this target is  i[3456789]86-*-elf) /*gcc-4.3.0/configure */

sincerely,
yakov

brian at dessent dot net wrote:
 --- Comment #1 from brian at dessent dot net  2008-03-24 19:54 ---
 Subject: Re:   New: Cannot build cross compiler for 
  i686-pc-linux-gnu: configure: error: Link tests are not allowed after 
  GCC_NO_EXECUTABLES

 yakov at emc dot com wrote:

   
 --target=i686-emc-elf --enable-languages=c++ --disable-multilib --with-gnu-as
 

 Your title for this bug is misleading as it seems you're building a
 cross for a newlib bare metal target, not i686-pc-linux-gnu.  That's
 just the host, and is irrelevant to the issue.

 There is currently a known problem with the libstdc++ configury and bare
 metal newlib targets.  You can fix it either by providing BSP files
 (crt*.o, linker script, etc) for your board so that test programs can be
 linked, or you can disable the AC_LIBTOOL_DLOPEN check in
 libstc++-v3/configure.ac for newlib targets, as in
 http://gcc.gnu.org/ml/gcc/2007-11/msg00790.html.  For a summary of the
 history of this issue:
 http://gcc.gnu.org/ml/gcc/2008-03/msg00515.html.


   


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35679