Re: reference to libgcc_s.so.1 without a corresponding run path

Bruce Korb wrote: Bob Friesenhahn wrote: On Wed, 1 Oct 2008, Bruce Korb wrote: /home/usr/bkorb/tools/ag/autogen-5.9.6pre15/_b/agen5/.libs/autogen: fatal: libgcc_s.so.1: open failed: No such file or directory Note that this problem is not libtool's fault. For very good reasons (e.g. many app

Re: reference to libgcc_s.so.1 without a corresponding run path

Bob Friesenhahn wrote: On Wed, 1 Oct 2008, Bruce Korb wrote: /home/usr/bkorb/tools/ag/autogen-5.9.6pre15/_b/agen5/.libs/autogen: fatal: libgcc_s.so.1: open failed: No such file or directory Note that this problem is not libtool's fault. For very good reasons (e.g. many applications stop work

Re: reference to libgcc_s.so.1 without a corresponding run path

On Wed, 1 Oct 2008, Bruce Korb wrote: /home/usr/bkorb/tools/ag/autogen-5.9.6pre15/_b/agen5/.libs/autogen: fatal: libgcc_s.so.1: open failed: No such file or directory Note that this problem is not libtool's fault. For very good reasons (e.g. many applications stop working if some old GCC is u

Re: reference to libgcc_s.so.1 without a corresponding run path

Ralf Wildenhues wrote: Hi Bruce, * Bruce Korb wrote on Wed, Oct 01, 2008 at 04:11:41AM CEST: cd ../getdefs ; gmake getdefs gmake[4]: Entering directory `/home/usr/bkorb/tools/ag/autogen-5.9.6pre15/_b/getdefs' top_builddir=.. top_srcdir=../.. PATH=`cd ../columns >/dev/null && pwd`:$PATH ; expo

reference to libgcc_s.so.1 without a corresponding run path (was: ltmain.sh (GNU libtool) 2.2)

Hi Bruce, * Bruce Korb wrote on Wed, Oct 01, 2008 at 04:11:41AM CEST: > cd ../getdefs ; gmake getdefs > gmake[4]: Entering directory > `/home/usr/bkorb/tools/ag/autogen-5.9.6pre15/_b/getdefs' > top_builddir=.. top_srcdir=../.. PATH=`cd ../columns >/dev/null && pwd`:$PATH > ; export top_builddir