This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Error in libstdc++
On Thursday 23 May 2002 16:49, Andreas Schwab wrote:
> Bo Thorsen <bo@sonofthor.dk> writes:
> |> I'm just testing a patch for x86-64 multilib support in mainline, but I
> |> get this error at the first c++ compile:
> |>
> |> make[4]: Entering directory
> |> `/suse/bo/Work/gcc/build-m2/x86_64-unknown-linux-gnu/libstdc++-v3/libmat
> |>h'
> |>
> |> /bin/sh ../libtool --mode=compile /suse/bo/Work/gcc/build-m2/gcc/xgcc
> |> -B/suse/bo/Work/gcc/build-m2/gcc/
> |> -B/suse/bo/Work/gcc/installed/x86_64-unknown-linux-gnu/bin/
> |> -B/suse/bo/Work/gcc/installed/x86_64-unknown-linux-gnu/lib/ -isystem
> |> /suse/bo/Work/gcc/installed/x86_64-unknown-linux-gnu/include
> |> -DHAVE_CONFIG_H -I. -I../../../../mainline/libstdc++-v3/libmath -I..
> |> -g -O2 -c ../../../../mainline/libstdc++-v3/libmath/stubs.c
> |>
> |> libtool: compile: unable to infer tagged configuration
> |> libtool: compile: specify a tag with `--tag'
> |>
> |> Any ideas what's wrong here?
>
> That usually happens when the compiler command line is different at
> compile time than at configure time, causing it to not match any of the
> tag configurations in the libtool script.
That seems reasonable enough. This was a bootstrap with multilib enabled, so
it probably went wrong the first time it tries "g++ -m32". Why isn't this a
problem for the other multilib architectures, there doesn't seem to be
anything multilib specific in libstdc++? In other words, how do I fix this :)
Bo.
--
Bo Thorsen | Praestevejen 4
Free software developer | 5290 Marslev
SuSE Labs | Denmark