* getting all build paths in environment
@ 2020-01-09 4:27 raingloom
2020-01-09 7:29 ` Gábor Boskovits
2020-01-09 20:12 ` Efraim Flashner
0 siblings, 2 replies; 3+ messages in thread
From: raingloom @ 2020-01-09 4:27 UTC (permalink / raw)
To: help-guix
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?
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: getting all build paths in environment
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
1 sibling, 0 replies; 3+ messages in thread
From: Gábor Boskovits @ 2020-01-09 7:29 UTC (permalink / raw)
To: raingloom; +Cc: help-guix
Hello,
raingloom <raingloom@riseup.net> ezt írta (időpont: 2020. jan. 9., Cs, 5:30):
>
> 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 can try the instructions here:
https://guix.gnu.org/manual/en/html_node/Debugging-Build-Failures.html
>
>
Best regards,
g_bor
--
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: getting all build paths in environment
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
1 sibling, 0 replies; 3+ messages in thread
From: Efraim Flashner @ 2020-01-09 20:12 UTC (permalink / raw)
To: raingloom; +Cc: help-guix
[-- 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 --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-01-09 20:13 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).