Sedat Dilek wrote:
> What means "libtool bug (already fixed)" and where is/was it fixed -
> upstream? In Debian package?
Last time, I ran into trouble with the copy of libtool in the gcc tree
(it would gobble up -B flags), and using the system libtool helped.
But now I can't reproduce that problem anymore --- it was probably
user error of some kind on my part.
I've just started a new gcc build with
$ git reset --hard origin/master
$ git clean -fdx
$ ./configure --prefix=$HOME/opt/gcc \
CFLAGS_FOR_TARGET="-g -O2 -B/usr/lib/x86_64-linux-gnu"
$ make BOOT_CFLAGS="-g -O2 -B/usr/lib/x86_64-linux-gnu"
To get a sense of where I am in the build process: the last line
output was
| /bin/sh ../libtool --tag CXX --mode=compile
/home/jrn/src/gcc/host-x86_64-unknown-linux-gnu/gcc/xgcc -shared-libgcc
-B/home/jrn/src/gcc/host-x86_64-unknown-linux-gnu/gcc -nostdinc++
-L/home/jrn/src/gcc/x86_64-unknown-linux-gnu/libstdc++-v3/src
-L/home/jrn/src/gcc/x86_64-unknown-linux-gnu/libstdc++-v3/src/.libs
-B/home/jrn/opt/gcc/x86_64-unknown-linux-gnu/bin/
-B/home/jrn/opt/gcc/x86_64-unknown-linux-gnu/lib/ -isystem
/home/jrn/opt/gcc/x86_64-unknown-linux-gnu/include -isystem
/home/jrn/opt/gcc/x86_64-unknown-linux-gnu/sys-include
-I/home/jrn/src/gcc/x86_64-unknown-linux-gnu/libstdc++-v3/include/x86_64-unknown-linux-gnu
-I/home/jrn/src/gcc/x86_64-unknown-linux-gnu/libstdc++-v3/include
-I/home/jrn/src/gcc/libstdc++-v3/libsupc++ -fno-implicit-templates -Wall
-Wextra -Wwrite-strings -Wcast-qual -fdiagnostics-show-location=once
-ffunction-sections -fdata-sections -frandom-seed=wlocale-inst.lo -g -O2
-D_GNU_SOURCE -c -o wlocale-inst.lo ../../.././libstdc++-v3/src/wlocale-inst.cc
Seems to be working well so far; I'm cautiously optimistic. gcc is
4.6.1-6, libc 2.13-16.
If that works, next step will be to try a build on i386. I'm
cautiously optimistic.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: http://lists.debian.org/[email protected]
