unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Michael Zucchi <notzed@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: guix build problem, no RUNPATH on libpthread.so
Date: Mon, 20 Apr 2020 16:20:41 +0200	[thread overview]
Message-ID: <CAJ3okZ0xnsRq39oS516BBDTcHYhLz++A8JtaD11gnFYB=nxX+g@mail.gmail.com> (raw)
In-Reply-To: <a280a6fa-08bd-6de8-03f1-f4ab5768bf1c@gmail.com>

Dear,

On Mon, 20 Apr 2020 at 11:56, Michael Zucchi <notzed@gmail.com> wrote:

[...]

> I ran guix environment guix --pure.

Which version (commit) of Guix do you use?
Could you provide the output of "guix describe"?


> Then I ran configure but it failed saying that guile 3.0 could not be
> found.  After some poking i found this is provided by the guile-next
> package, so I had to manually install that.  So the instructions didn't
> work right off the bat but configure then completed just fine.

Which commit of the repo are you trying to compile?


> However make then fails:

Depending on when was the last "guix pull" and when was the last "git
pull" and what you already compiled month ago, failing could happen;
especially because Guile has been updated from 2 to 3.

After updating "guix pull" and "git pull", you could try:

  guix environment guix --pure
  make distclean
  ./configure --localstatedir=/var/
  make


Hope that helps.

All the best,
simon

  reply	other threads:[~2020-04-20 14:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20  9:55 guix build problem, no RUNPATH on libpthread.so Michael Zucchi
2020-04-20 14:20 ` zimoun [this message]
2020-04-21  0:11   ` Michael Zucchi
2020-04-21  5:36     ` Efraim Flashner
2020-04-21  7:55       ` zimoun
2020-04-22  0:35         ` bug#40740: " Michael Zucchi

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='CAJ3okZ0xnsRq39oS516BBDTcHYhLz++A8JtaD11gnFYB=nxX+g@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=notzed@gmail.com \
    /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).