This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Failure to run testsuite with libstdc++-v3


In article <398FC548.336F9737@telia.com>,
Christian Jönsson <c.christian.joensson@telia.com> writes:

> This is on a Red Hat Linux 6.2/Intel system up to date as of
> 2000-08-07. It's kernel-2.2.16-3 and binutils-2.9.5.0.22-6.

> Here's today's snapshot. I did this:

> ../gcc/configure --enable-threads --enable-shared --enable-libstdcxx-v3
> (make bootstrap-lean >& build.log;
> make RUNTESTFLAGS="--target_board 'unix{-fPIC,-fpic,}'" -k check >&
> check.log) &

> same problem:

> Running /usr/local/src/gcc/gcc/testsuite/g++.dg/special/ecos.exp ...
> couldn't execute
> "/usr/local/src/objdir-egcs-20000808/i686-pc-linux/libstdc++-v3/mkcheck":
> no such file or directory
>     while executing
> "exec ${odir_v3}/mkcheck 2 ${odir_v3} ${sdir_v3}"
>     (procedure "g++_include_flags" line 23)
>     invoked from within

The problem is that libstdc++-v3 wasn't actually successfully
configured nor built:

(From the log file you sent:)

checking for enabled cshadow headers... no
checking for threads package to use... configure: error:  is an unknown thread p
ackage

[Configure in libstdc++-v3 aborted here without halting the top-level
 `make bootstrap' step with an error.  Had everything worked right,
 then many additional build commands would have appeared here in the
 log.  Next, it continued configuring other packages and going on its
 merry way:]

Configuring in i686-pc-linux/libf2c

The user-level solution is to explicitly enable posix threads:

../gcc/configure --enable-threads=posix --enable-shared --enable-libstdcxx-v3

The developer-level solution is more complex with many possible
solutions.

Regards,
Loren

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]