D.gnu - C compiler cannot create executables?
- dsimcha (43/43) Sep 26 2011 I keep getting the following error on two newly set up Debian testing
- Andrew Wiley (9/50) Sep 26 2011 omp':
- =?UTF-8?B?IkrDqXLDtG1lIE0uIEJlcmdlciI=?= (11/18) Sep 26 2011 =2E.. snip ...
- Iain Buclaw (11/29) Sep 26 2011 For Debian/Ubuntu, you also need to consider that they've been experimen...
I keep getting the following error on two newly set up Debian testing boxes, as well as a Ubuntu Oneric box, when building GDC tip using GCC 4.6.1: checking for x86_64-unknown-linux-gnu-gcc... /var/tmp/gdcStuff/gdc/dev/gcc-4.6.1/objdir/./gcc/xgcc -B/var/tmp/gdcStuff/gdc/dev/gcc-4.6.1/objdir/./gcc/ -B/gdc/x86_64-unknown-linux-gnu/bin/ -B/gdc/x86_64-unknown-linux-gnu/lib/ -isystem /gdc/x86_64-unknown-linux-gnu/include -isystem /gdc/x86_64-unknown-linux-gnu/sys-include checking for C compiler default output file name... configure: error: in `/var/tmp/gdcStuff/gdc/dev/gcc-4.6.1/objdir/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 `/var/tmp/gdcStuff/gdc/dev/gcc-4.6.1/objdir' make[1]: *** [stage1-bubble] Error 2 make[1]: Leaving directory `/var/tmp/gdcStuff/gdc/dev/gcc-4.6.1/objdir' make: *** [all] Error 2 Somehow, this error does not occur on my work box, where I run Ubuntu 10.04. I have no idea what the difference is. Below is my (very quick-and-dirty) build script, mostly cut and pasted from the GDC wiki. rm -rf /var/tmp/gdcStuff mkdir /var/tmp/gdcStuff cd /var/tmp/gdcStuff hg clone https://bitbucket.org/goshawk/gdc mkdir gdc/dev cd gdc/dev tar -xvf ../../gcc-4.6.1.tar.bz2 cd gcc-4.6.1 ln -s ../../../d gcc/d ./gcc/d/setup-gcc.sh -v2 mkdir objdir cd objdir ../configure --enable-languages=d,c++ --disable-shared \ --prefix=/gdc --enable-multilib \ --with-bugurl="https://bitbucket.org/goshawk/gdc/issues" \ --enable-checking=release number of cores in the -j argument make install DESTDIR=$HOME/apps
Sep 26 2011
On Mon, Sep 26, 2011 at 6:11 PM, dsimcha <dsimcha yahoo.com> wrote:I keep getting the following error on two newly set up Debian testing box=es,as well as a Ubuntu Oneric box, when building GDC tip using GCC 4.6.1: checking for x86_64-unknown-linux-gnu-gcc... /var/tmp/gdcStuff/gdc/dev/gcc-4.6.1/objdir/./gcc/xgcc -B/var/tmp/gdcStuff/gdc/dev/gcc-4.6.1/objdir/./gcc/ -B/gdc/x86_64-unknown-linux-gnu/bin/ -B/gdc/x86_64-unknown-linux-gnu/lib/ -isystem /gdc/x86_64-unknown-linux-gnu/include -isystem /gdc/x86_64-unknown-linux-gnu/sys-include checking for C compiler default output file name... configure: error: in `/var/tmp/gdcStuff/gdc/dev/gcc-4.6.1/objdir/x86_64-unknown-linux-gnu/libg=omp':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 `/var/tmp/gdcStuff/gdc/dev/gcc-4.6.1/objdir' make[1]: *** [stage1-bubble] Error 2 make[1]: Leaving directory `/var/tmp/gdcStuff/gdc/dev/gcc-4.6.1/objdir' make: *** [all] Error 2 Somehow, this error does not occur on my work box, where I run Ubuntu 10.=04.=A0I have no idea what the difference is. =A0Below is my (very quick-and-=dirty)build script, mostly cut and pasted from the GDC wiki. rm -rf /var/tmp/gdcStuff mkdir /var/tmp/gdcStuff cd /var/tmp/gdcStuff hg clone https://bitbucket.org/goshawk/gdc mkdir gdc/dev cd gdc/dev tar -xvf ../../gcc-4.6.1.tar.bz2 cd gcc-4.6.1 ln -s ../../../d gcc/d ./gcc/d/setup-gcc.sh -v2 mkdir objdir cd objdir ../configure --enable-languages=3Dd,c++ --disable-shared \ =A0 =A0--prefix=3D/gdc --enable-multilib \ =A0 =A0--with-bugurl=3D"https://bitbucket.org/goshawk/gdc/issues" \ =A0 =A0--enable-checking=3Drelease make -j 2 2>&1 | tee build.log =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =number of cores in the -j argument make install DESTDIR=3D$HOME/appsHave you searched for the error in config.log? That basically means that the default set of options that configure is using is causing GCC to get an error.
Sep 26 2011
Andrew Wiley wrote:On Mon, Sep 26, 2011 at 6:11 PM, dsimcha <dsimcha yahoo.com> wrote:boxes,I keep getting the following error on two newly set up Debian testing =as well as a Ubuntu Oneric box, when building GDC tip using GCC 4.6.1:==2E.. snip ...Have you searched for the error in config.log? That basically means that the default set of options that configure is using is causing GCC to get an error.My bet is that the error is along the lines of "Cannot find cc1". If that is the case, it means you have the current directory (".") in your path. You need to remove it. Jerome --=20 mailto:jeberger free.fr http://jeberger.free.fr Jabber: jeberger jabber.fr
Sep 26 2011
== Quote from "Jérôme M. Berger" (jeberger free.fr)'s articleThis is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigEFBBD89E592FB5B6388005AB Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Andrew Wiley wrote:For Debian/Ubuntu, you also need to consider that they've been experimenting with multiarch system for 32 and 64bit, which requires special patches to GCC so that it can find the correct locations of headers, libraries, etc. If you are using a vanilla GCC tarball to build, it may help if you put the following in your .bashrc LIBRARY_PATH=/usr/lib/i386-linux-gnu CPATH=/usr/include/i386-linux-gnu export LIBRARY_PATH CPATH Regards IainOn Mon, Sep 26, 2011 at 6:11 PM, dsimcha <dsimcha yahoo.com> wrote:boxes,I keep getting the following error on two newly set up Debian testing ==2E.. snip ...as well as a Ubuntu Oneric box, when building GDC tip using GCC 4.6.1:=Have you searched for the error in config.log? That basically means that the default set of options that configure is using is causing GCC to get an error.My bet is that the error is along the lines of "Cannot find cc1". If that is the case, it means you have the current directory (".") in your path. You need to remove it. Jerome
Sep 26 2011
dsimcha <dsimcha yahoo.com> On 9/27/2011 1:44 AM, Iain Buclaw wrote:For Debian/Ubuntu, you also need to consider that they've been experimenting with multiarch system for 32 and 64bit, which requires special patches to GCC so that it can find the correct locations of headers, libraries, etc. If you are using a vanilla GCC tarball to build, it may help if you put the following in your .bashrc LIBRARY_PATH=/usr/lib/i386-linux-gnu CPATH=/usr/include/i386-linux-gnu export LIBRARY_PATH CPATHThanks. I ended up figuring out the same thing almost simultaneously. I solved it slightly differently by adding a few symlinks for important files to my /usr/lib and /usr/include/gnu directories.
Sep 27 2011
== Quote from Iain Buclaw (ibuclaw ubuntu.com)'s articleFor Debian/Ubuntu, you also need to consider that they've been experimenting with multiarch system for 32 and 64bit, which requires special patches to GCC so that it can find the correct locations of headers, libraries, etc. If you are using a vanilla GCC tarball to build, it may help if you put the following in your .bashrc LIBRARY_PATH=/usr/lib/i386-linux-gnu CPATH=/usr/include/i386-linux-gnu export LIBRARY_PATH CPATH Regards IainAnother way to fix this is apparently to just disable the bootstrap feature via --disable-bootstrap. It seems rather useless anyhow. Why should I care what my compiler was compiled with?
Sep 27 2011