From: Efraim Flashner <efraim@flashner.co.il>
To: raingloom <raingloom@riseup.net>
Cc: help-guix@gnu.org
Subject: Re: getting all build paths in environment
Date: Thu, 9 Jan 2020 22:12:27 +0200 [thread overview]
Message-ID: <20200109201227.GB1370@E5400> (raw)
In-Reply-To: <a950f13f26a557978cdc93d05b5d096a4577cb89.camel@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
On Thu, Jan 09, 2020 at 05:27:07AM +0100, raingloom wrote:
> I'm trying to bootstrap Go for Plan 9, this should be as simple as
> setting a few environment variables and running a script, but during
> the third phase, I run into this:
>
> /home/raingloom/Projects/Plan9/go64/go-plan9-arm64-bootstrap/bin/go:
> error while loading shared libraries: libgcc_s.so.1: cannot open shared
> object file: No such file or directory
>
> as far as I know, this would work if libgcc was in the relevant search
> path.
>
> Is there a way I could set up the same environment that guix leaves in
> /tmp/guix-.../environment-variables after a failed build?
>
You want the environmental-variables file at
/tmp/guix-build-file-version.drv-X/environmental-variables. You can
source the file directly after 'guix environment --pure foo' and that
should give you something approaching the build environment.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-01-09 20:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 4:27 getting all build paths in environment raingloom
2020-01-09 7:29 ` Gábor Boskovits
2020-01-09 20:12 ` Efraim Flashner [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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200109201227.GB1370@E5400 \
--to=efraim@flashner.co.il \
--cc=help-guix@gnu.org \
--cc=raingloom@riseup.net \
/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).