This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: build errors with current trunk (r144530)
- From: Benjamin Kosnik <bkoz at redhat dot com>
- To: tfogal at sci dot utah dot edu
- Cc: tfogal at alumni dot unh dot edu, libstdc++ at gcc dot gnu dot org
- Date: Mon, 2 Mar 2009 10:43:27 -0800
- Subject: Re: build errors with current trunk (r144530)
- References: <auto-000018808884@sci.utah.edu>
> Hi, I'm getting build errors in libstdc++ on an x86_64 host.
You should be trying to match known-good tests results here:
http://gcc.gnu.org/ml/gcc-testresults/2009-03/msg00181.html
> It appears like I'm not setting up libtool correctly (long lines
> snipped a bit):
You shouldn't be setting up libtool at all.
;)
> My configure line is filled with many options [1], most of which I
> pulled from the gcc -v line of a known working gcc on a similar host.
Read:
http://gcc.gnu.org/install/
and
http://gcc.gnu.org/install/configure.html
> Any ideas what I'm screwing up?
> export CFLAGS="${CFLAGS} -m64 -fPIC -I${PREFIX}/include"
> export CPPFLAGS="${CPPFLAGS} -I${PREFIX}/include"
> export CXXFLAGS="${CXXFLAGS} -m64 -fPIC -I${PREFIX}/include"
> export LDFLAGS="${LDFLAGS} -m64 -L${PREFIX}/lib64 -L${PREFIX}/lib"
Should be no need to do this.
> ../gcc-trunk/configure \
> --prefix=${HOME}/sw \
> --enable-languages=c++ \
> --enable-checking=release \
> --disable-werror \
> --with-system-zlib \
> --enable-__cxa_atexit \
> --disable-libstdcxx-pch \
> --disable-multilib \
> --with-mpfr=${PREFIX}
Would do it, I would think.
You should start with the smallest, most default configure, get
something working, and only add the options you need. Look at the way
the compiler is configured on the gcc-testresults link above.
Please direct follow-ups to gcc-help.
-benjamin