[Bug compile/23671] New: compile command dlopens wrong libcc1.so

[sandra at codesourcery dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=23671

Bug ID: 23671
Summary: compile command dlopens wrong libcc1.so
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: compile
Assignee: unassigned at sourceware dot org
Reporter: sandra at codesourcery dot com
Target Milestone: ---

The "compile" command attempts to dlopen "libcc1.so". Since there is no slash
in that filename, dlopen searches LD_LIBRARY_PATH... and it's finding the
"libcc1.so" for the host system's GCC, rather than one that goes with the GCC
for the target. I verified this with strace. In fact, we don't configure GCC
to build libcc1.so for our nios2 cross-toolchains, so there is nothing for it
to find.

Maybe the right thing to do here is a configure-time option to specify a
binary-relative pathname instead of hardwiring "libcc1.so", and perhaps another
option to disable the "compile" feature entirely when it's not expected to
work?