This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug testsuite/63719] New: gcc-set-multilib-library-path usage outside of gcc/testsuite/
- From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 03 Nov 2014 08:34:05 +0000
- Subject: [Bug testsuite/63719] New: gcc-set-multilib-library-path usage outside of gcc/testsuite/
- Auto-submitted: auto-generated
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63719
Bug ID: 63719
Summary: gcc-set-multilib-library-path usage outside of
gcc/testsuite/
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: tschwinge at gcc dot gnu.org
I noticed that several target libraries' test harnesses (currently: libatomic,
libgomp, libitm, libvtv) use
gcc/testsuite/lib/gcc-defs.exp:gcc-set-multilib-library-path to append to
LD_LIBRARY_PATH, but that function only actually does something if rootme is
set, which is only done in the site.exp generated by gcc/Makefile.in, which
these target libraries' test harnesses are not using, as far as I can tell.
This problem has been existing "forever", and apparently is not causing any ill
effects?