C compiler cannot create executables?

[Andrew Wiley]

On Mon, Sep 26, 2011 at 6:11 PM, dsimcha <dsimcha at yahoo.com> wrote:
> 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
> cp -R * /var/tmp/gdcStuff  # Copies the gcc bzip file
> 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
> make -j 2 2>&1 | tee build.log                            # insert your
> number of cores in the -j argument
> make install DESTDIR=$HOME/apps
>
>

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.