bootstrap failure: libstdc++-v3/include/stdc++.h:83

Gerald Pfeifer gerald@pfeifer.com
Wed Jul 9 22:41:00 GMT 2003


On Wed, 9 Jul 2003, Mark Mitchell wrote:
> I'm having trouble building on FreeBSD due to problems with iconv.
>
> gcc   -g -O2 -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes
> -Wmissing-\prototypes -pedantic -Wno-long-long -fno-common
> -DHAVE_CONFIG_H  -o cc1 \
>         c-parse.o c-lang.o c-pretty-print.o attribs.o c-errors.o c-lex.o
> c-prag\ma.o c-decl.o c-typeck.o c-convert.o c-aux-info.o c-common.o
> c-opts.o c-format.\o c-semantics.o c-incpath.o cppdefault.o c-ppoutput.o
> c-cppbuiltin.o prefix.o c\-objc-common.o c-dump.o c-pch.o libcpp.a
> main.o libbackend.a ../libiberty/libi\berty.a /usr/local/lib/libintl.so
> -rpath /usr/local/lib -liconv
> /usr/libexec/elf/ld: cannot find -liconv
>
> On this machine, libiconv is in /usr/local/lib.  What's going wrong
> here?

I tried  to reproduce this (also using objdir as a subdirectory of srcdir,
which is different from my regular setup), but the corresponding line from
my build looks as follows:

  gcc    -g -DIN_GCC  -W -Wall -Wwrite-strings -Wstrict-prototypes
  -Wmissing-prototypes -pedantic -Wno-long-long -fno-common
  -DHAVE_CONFIG_H  -o cc1
  c-parse.o c-lang.o c-pretty-print.o attribs.o c-errors.o c-lex.o
  c-pragma.o c-decl.o c-typeck.o  c-convert.o c-aux-info.o c-common.o
  c-opts.o c-format.o c-semantics.o  c-incpath.o cppdefault.o c-ppoutput.o
  c-cppbuiltin.o prefix.o c-objc-common.o c-dump.o c-pch.o libcpp.a
  main.o libbackend.a ../libiberty/libiberty.a ../intl/libintl.a

...which differs in the last few lines.

I configured with
  ../configure --prefix=/files/pfeifer/ngcc --enable-languages=c,c++
Did you use something else (modulo the prefix)?

One observation: why is there /usr/local/lib/libintl.so on the one hand,
and -rpath /usr/local/lib -liconv on the other hand?  That is, why is
libiconv not fully qualified whereas libintil.so is?

And why are you getting /usr/local/lib/libintl.so instead of "Zacks'"
../intl/libintl.a?  Something seems fishy here!

Gerald
-- 
Gerald Pfeifer (Jerry)   gerald@pfeifer.com   http://www.pfeifer.com/gerald/



More information about the Gcc mailing list