From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guix-devel@gnu.org, 24544-done@debbugs.gnu.org,
Jan Nieuwenhuizen <janneke@gnu.org>
Subject: bug#24544: 2.1.4 tarball install fails on GuixSD
Date: Sun, 12 Mar 2017 20:04:52 +0100 [thread overview]
Message-ID: <87lgsas4dn.fsf__20625.1525473364$1489345578$gmane$org@pobox.com> (raw)
In-Reply-To: <87k27w82uy.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sat, 11 Mar 2017 12:33:25 +0100")
On Sat 11 Mar 2017 12:33, ludo@gnu.org (Ludovic Courtès) writes:
> Andy Wingo <wingo@pobox.com> skribis:
>
>> On Sun 25 Sep 2016 21:22, Jan Nieuwenhuizen <janneke@gnu.org> writes:
>>
>>> ld-wrapper: error: attempt to use impure library "/home/janneke/guile-2.1.4/lib/libguile-2.2.so"
>>> collect2: error: ld returned 1 exit status
>>> libtool: error: error: relink 'guile-readline.la' with the above command before installing it
>>
>> This is because Guix is silly and thinks that even when you are
>> installing to /rando/prefix/that/you/like that it's bad to link to
>> thinks outside /gnu/store.
>>
>> The workaround is to export GUIX_LD_WRAPPER_ALLOW_IMPURITIES=yesplease.
>> (Actually any value.)
>>
>> The real fix is to prevent ld-wrapper from carping for normal installs
>> to non-store prefixen!
>
> Do you mean we should change the default? That is,
> GUIX_LD_WRAPPER_ALLOW_IMPURITIES=yes by default, and gnu-build-system
> would set it to “no”.
I think I didn't know precisely what I meant :) However! That sounds
like a good idea -- the benefits of the check are only intended for Guix
builds, so builds outside Guix should probably not go through that
check.
Andy
prev parent reply other threads:[~2017-03-12 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-25 19:22 bug#24544: 2.1.4 tarball install fails on GuixSD Jan Nieuwenhuizen
2017-02-22 22:22 ` Andy Wingo
[not found] ` <87vas1x3un.fsf@pobox.com>
2017-03-11 11:33 ` Ludovic Courtès
[not found] ` <87k27w82uy.fsf@gnu.org>
2017-03-12 19:04 ` Andy Wingo [this message]
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='87lgsas4dn.fsf__20625.1525473364$1489345578$gmane$org@pobox.com' \
--to=wingo@pobox.com \
--cc=24544-done@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=janneke@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).