From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Relocatable installation
Date: Mon, 31 Jan 2011 22:18:28 +0100 [thread overview]
Message-ID: <1296508708.17905.47.camel@vuurvlieg> (raw)
In-Reply-To: <871v3s4wlh.fsf@gnu.org>
[cc: list]
Ludovic Courtès schreef op ma 31-01-2011 om 22:00 [+0100]:
Hi,
> Your patch lacks this RPATH magic, though.
Yes, we have that in our GUB cross build system. Possibly this
is a thing/feature request for libtool.
> Perhaps it should check
> whether ‘-Wl,-rpath='$ORIGIN/../lib'’ works?
That would be a nice feature. I expect that if you want to
use this, you should know what you're doing anyway...
> Is ‘-Wl,-z -Wl,origin’
> needed as well when linking ‘guile’?
No, we only use
-Wl,-rpath -Wl,'$'ORIGIN/../lib
We do that by postprocessing libtool, substituting the
hardcode_libdir_flag_spec, of course, something like:
([('^(hardcode_libdir_flag_spec)=".+"', 'hardcode_libdir_flag_spec="-Wl,-rpath -Wl,\\$libdir -Wl,-rpath -Wl,\'$\'ORIGIN/../lib -Wl,-rpath -Wl,/home/janneke/vc/gub/target/mingw/root/usr/lib"')], '/home/janneke/vc/gub/target/mingw/build/guile-1.9.14/libtool')
> Yes, that’s what I meant: it only works as long as users touch only
> $prefix, not $libdir, $bindir, etc.
Sure. Dropping a binary package in a random place is a
common way to do exactly that.
> Then I have nothing against this option, as long as it’s off by default.
Great, thanks!
Jan.
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl
next prev parent reply other threads:[~2011-01-31 21:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-29 19:41 cross building 1.9.14 for mingw Jan Nieuwenhuizen
2011-01-29 21:34 ` Ludovic Courtès
2011-01-31 20:16 ` Jan Nieuwenhuizen
2011-01-31 20:44 ` Ludovic Courtès
2011-02-15 10:20 ` Jan Nieuwenhuizen
2011-02-22 8:34 ` Andy Wingo
2011-02-24 9:39 ` Jan Nieuwenhuizen
2011-02-24 10:37 ` Ludovic Courtès
2011-03-04 11:11 ` problems solved by AC_LIB_HAVE_LINKFLAGS [was: cross building 1.9.14 for mingw] Andy Wingo
2011-03-20 8:08 ` Jan Nieuwenhuizen
2011-03-20 8:21 ` Ralf Wildenhues
2011-03-20 8:34 ` Jan Nieuwenhuizen
2011-03-20 8:56 ` Ralf Wildenhues
2011-01-29 21:39 ` Relocatable installation Ludovic Courtès
2011-01-31 20:26 ` Jan Nieuwenhuizen
2011-01-31 20:50 ` Andy Wingo
2011-01-31 20:55 ` Jan Nieuwenhuizen
2011-01-31 21:30 ` Andy Wingo
2011-01-31 21:49 ` Jan Nieuwenhuizen
2011-01-31 21:00 ` Ludovic Courtès
2011-01-31 21:18 ` Jan Nieuwenhuizen [this message]
2011-01-31 22:09 ` Ludovic Courtès
2011-01-31 22:26 ` Jan Nieuwenhuizen
2011-02-14 12:29 ` cross building 1.9.14 for mingw Ludovic Courtès
2011-02-15 10:02 ` Jan Nieuwenhuizen
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=1296508708.17905.47.camel@vuurvlieg \
--to=janneke@gnu.org \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
/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).