[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [GNU Bison 1.875d] testsuite: 43 84 85 86 87 88 89 110 failed

From: Vin Shelton
Subject: Re: [GNU Bison 1.875d] testsuite: 43 84 85 86 87 88 89 110 failed
Date: Mon, 24 May 2004 21:13:48 -0400

Paul Eggert <address@hidden> writes:

> Thanks for your bug report.  From your logs it appears that your C++
> compiler by default doesn't build executables that actually run.  This
> is an unfortunate property of the default GCC installation these days
> if you install GCC yourself.  I don't really understand why GCC does
> it that way.  Anyway, this problem caused all the C++-related tests to
> fail even though Bison itself was just fine.  I have installed the
> following patch so that future Bison testers don't run into the
> problem.

Thanks for the followup, Paul.  I know the problem with g++ binaries
pretty well - I've stumbled across it before.  Thanks for pointing
that out to me.  I'm a little confused about how to pass the
appropriate LDFLAGS to the test harness, though.  Here's what I did:

  1. ../../src/bison-1.875d/configure '--prefix=/usr/local'
     '--disable-nls' LDFLAGS="-R$USRLOCAL/gcc/lib"
  2. make
  3. cd tests
  4. /bin/sh ../../../src/bison-1.875d/tests/testsuite 43
ERROR: 1 test was run,
1 failed unexpectedly.
  5. ldd testsuite.dir/043/input
        libstdc++.so.6 => not found
        libm.so.6 => /lib/i686/libm.so.6 (0x40024000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x40046000)
        libc.so.6 => /lib/i686/libc.so.6 (0x4004f000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

libstdc++.so.6 lives in /usr/local/gcc/lib, so what's the problem?
How do I pass LDFLAGS to the testsuite?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]