> icc users:
>
> Aparently support for icc isn't complete. Here is where
> you can help by submitting a patch that fixes the problems
> you're running into. I don't have access to this compiler,
> so if it is something you want, you'll have to volunteer to
> do it. Please read http://www.gnu.org
On my custom-built GNU/Linux systems, glibc is not installed in the
usual place. Passing the appropriate -I, -L, and -Wl,-R, flags is
often enough to build most things. I've found some additional
problems with libtool-based packages, though.
- Some (older?) versions of ltconfig look for /lib/libc
Hi Libtool'ers,
I've written a bug report to [EMAIL PROTECTED], but no one seems to
have noticed. I think at least the second problem is worth
addressing. Please take a look at:
http://mail.gnu.org/archive/html/bug-libtool/2003-01/msg00030.html
Yours,
___ | Christian Holm Christensen
I have problems with hardcoded paths to shared libraries on HP-UX. When
libtool creates executable or shared library, it hardcodes paths to any
dependency libraries into it and disable dynamic lookup according to
SHLIB_PATH shell variable. Now when I move the library to different
directory, dyn
