Asfand Yar Qazi kirjoitti:
Kai Ruottu wrote:
Whatever went wrong, can be seen in that 'config.log' in the directory
where the configure failed !
> There's nothing of benefit in config.log, especially since I can't
find the one this
> particular command refers to.
So running a 32-bit application during the libstdc++-v3 configure
somehow didn't
succeed. This is the clue... Maybe it is hard to find what failed
there, which shouldn't
fail, but nobody else than you can do that...
I can only ask stupid questions like: "Does the new GCC work when
trying something
very simple? Doing the following:
1. build only GCC : 'make all-gcc'
2. install only GCC: 'make install-gcc'
3. try compiling and linking a 32-bit "Hello World"
4. ask about the error got with it here if this simple "sanity test" failed
could lead to some progress in this.... But I cannot believe you didn't
do this before
asking anything. If the new GCC doesn't work with "Hello World", it is
quite sure
that those simple compile & link tests in the libstdc++-v3 configure
would fail too.
It is insane to even try to build libiberty, libstdc++ etc. if the new
compiler with the
binutils and the target C library cannot even produce a Hello World...
It is expected
being capable to do that, so the extra target libraries are tried to be
produced.
