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]
Other format: [Raw text]

Re: G++ test suite picking up incorrect libstc++


Paolo Carlini wrote:
On 10/22/2010 08:43 PM, Michael Eager wrote:
Hi --

I'm seeing test suite failures in g++ caused by
linking with the wrong libstdc++.so.

It looks like g++.exp always appends the default
directory
  append flags -L${gccpath}/libstdc++-v3/src/.libs
instead of
  append flags -L${gccpath}/<multilib>/libstdc++-v3/src/.libs

Without having looked into the issue in any detail, the issue seems
weird to me: for sure many people regularly build multilib (myself and
HJ on gcc-testresults included, for example) without any problem
whatsoever. I would suggest figuring out first what's special about your
setup.

I don't know that there's anything special about my setup. g++.exp is adding -L paths to the wrong libstdc++ directory. When running GCC tests, only the -B option is added. The correct multilib directory is selected by the gcc driver.

Do you run "make check" with default options, or do you
specify compiler options which should result in linking
non-default c++ libraries?

I'm going to run the test_installed script.  This should
use the gcc driver to select the multilib, rather than g++.exp.

--
Michael Eager	 eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077


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