From: Rob Browning <rlb@defaultvalue.org>
Cc: Marius Vollmer <mvo@zagadka.ping.de>,
guile-devel@gnu.org, Guile Mailing List <guile-user@gnu.org>
Subject: Re: Guile 1.5.6 beta available for testing.
Date: Tue, 12 Mar 2002 10:19:27 -0600 [thread overview]
Message-ID: <87henllpww.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0203112051530.2317-100000@ariel.lan.telltronics.org> (Steve Tell's message of "Mon, 11 Mar 2002 21:32:30 -0500 (EST)")
Steve Tell <tell@telltronics.org> 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
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next parent reply other threads:[~2002-03-12 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0203112051530.2317-100000@ariel.lan.telltronics.org>
2002-03-12 16:19 ` Rob Browning [this message]
2002-03-15 20:54 ` Guile 1.5.6 beta available for testing Marius Vollmer
[not found] <m38z8xly2v.fsf@appel.lilypond.org>
2002-03-12 16:23 ` Rob Browning
2002-03-15 20:57 ` Marius Vollmer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87henllpww.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=mvo@zagadka.ping.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).