From: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
To: "gentoo-dev@lists.gentoo.org" <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] [EAPI 7] Cross-compile improvements (BDEPEND, BROOT, sysroot)
Date: Thu, 3 Dec 2015 08:22:01 +0000 [thread overview]
Message-ID: <1449130978.14754.49.camel@infinera.com> (raw)
In-Reply-To: <20151201225855.20b17a34@symphony.aura-online.co.uk>
On Tue, 2015-12-01 at 22:58 +0000, James Le Cuirot wrote:
>
[SNIP really good writeup, thanks :)]
> There's also a further complication here that I forgot to mention to
> mgorny. While calling configure with --with-sysroot certainly helps,
> it still stumbles on a significant number of packages that do
> relinking at the end of the build if elibtoolize hasn't been called.
> elibtoolize has long patched ltmain.sh with ELT-patches/cross/link-ROOT
I looked at ELT-patches/cross/link-ROOT and it has
--- libltdl/config/ltmain.sh 2008-09-07 19:56:33.000000000 +0200
+++ libltdl/config/ltmain.sh.new 2009-02-15 20:37:47.000000000 +0100
@@ -5768,7 +5768,7 @@
test "$hardcode_direct_absolute" = no; then
add="$libdir/$linklib"
elif test "$hardcode_minus_L" = yes; then
- add_dir="-L$libdir"
+ add_dir="-L$ROOT/$libdir"
add="-l$name"
elif test "$hardcode_shlibpath_var" = yes; then
case :$finalize_shlibpath: in
@@ -5785,7 +5785,7 @@
fi
else
# We cannot seem to hardcode it, guess we'll fake it.
- add_dir="-L$libdir"
+ add_dir="-L$ROOT/$libdir"
I think this should be "add_dir=-L$lt_sysroot$libdir" rather than ROOT.
See also bug https://bugs.gentoo.org/show_bug.cgi?id=521184
and since I think this is also a libool bug there is a post upstream
http://lists.gnu.org/archive/html/libtool/2015-10/msg00012.html
This has not gotten any attention from upstream libtool folks. Would
be great if someone more could push for such a change.
Jocke
> when cross-compiling and this still applies to the very latest libtool.
> I filed several bugs about this before realising that fixing this
> globally would be better. elibtoolize doesn't require anything to be
> installed and the description does say "this function should always be
> safe to run" but I suppose calling it unconditionally might screw up
> patching in some isolated cases. What do you think?
>
> Phew, I'm done. Please be gentle! :)
>
next prev parent reply other threads:[~2015-12-03 8:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 22:58 [gentoo-dev] [EAPI 7] Cross-compile improvements (BDEPEND, BROOT, sysroot) James Le Cuirot
2015-12-02 11:40 ` Alexis Ballier
2015-12-02 23:20 ` James Le Cuirot
2015-12-03 8:28 ` Alexis Ballier
2015-12-06 21:05 ` Joakim Tjernlund
2015-12-06 21:15 ` James Le Cuirot
2015-12-07 13:47 ` Alexis Ballier
2015-12-15 5:27 ` Mike Frysinger
2015-12-03 8:22 ` Joakim Tjernlund [this message]
2015-12-03 23:32 ` James Le Cuirot
2015-12-04 7:14 ` Joakim Tjernlund
2015-12-03 16:21 ` Guilherme Amadio
2015-12-05 19:00 ` Gregory M. Turner
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1449130978.14754.49.camel@infinera.com \
--to=joakim.tjernlund@infinera.com \
--cc=gentoo-dev@lists.gentoo.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