Re: Guile 1.5.6 beta available for testing.

[Rob Browning]

Steve Tell <address@hidden> writes:

> I found two workarounds that involve hacking the libtool script.  
> Both get libtool to link libguile into libguilereadline as
> "/usr/guile-1.5.6/lib/libguile.so" instead of "-lguile". Even though
> -L/usr/lib remains on the gcc command line, this does the right thing.

Another possibility might be for us to just add a ./overrides/gcc and
then in our Makefiles export PATH=`pwd`/overrides:${PATH}.  Inside
this gcc override script, we could strip out any offending
-L\s*/usr/lib(/)? and -I\s*/usr/include(/)? occurrences before
calling.

  export PATH=`filter-out-parent-dir ${PATH}`
  exec "$@"

Ugly, but if -L /usr/lib and -I /usr/include are the problem, this
should fix it.  Of course we'd have to symlink to cc, etc. as well for
non-gcc platforms, and this won't help if they don't all use -L and
-I :/

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD