From: Marco van Hulten <marco@hulten.org>
To: help-guix <help-guix@gnu.org>
Subject: Re: racket patch not found
Date: Sun, 15 Jul 2018 12:39:37 +0200 [thread overview]
Message-ID: <20180715123937.3d08373a@jasniac.instanton> (raw)
In-Reply-To: <87pnzpr1rf.fsf@netris.org>
Hi Mark, others—
Je 14 jul 16:38 skribis Mark:
> Marco van Hulten <marco@hulten.org> writes:
>
> > When I install the package `racket' through
> >
> > guix pull &&\
> > guix package -i racket
> >
> > I get this error:
> >
> > guix package: error: racket-fix-xform-issue.patch: patch not found
>
> This was fixed in commit 57ac5261fec345b16cf80f87aa03212abc2c5a11,
> pushed a few days ago.
>
> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=57ac5261fec345b16cf80f87aa03212abc2c5a11
>
> If you "guix pull" and try again, hopefully it will work now.
Yes, it does!
It did warn me about no readline support:
$ racket
Welcome to Racket v6.12.
; Warning: no readline support (ffi-lib: couldn't open "libedit.so.3" (libedit.so.3: cannot open shared object file: No such file or directory))
>
So I installed libedit, but the warning stays and I have still no
readline support.
Maybe I have to do add it to my LD_LIBRARY_PATH or something. Instead,
I went looking for libedit.so.3, but it wasn't in ~/.guix-profile/lib/.
When I started racket from that working directory, the warning wasn't
given and I had readline support. According to my experience binaries
indeed look in the working directory for libraries. Apparently racket
finds the useful library in ~/.guix-profile/lib/. But what file is it,
and why does it not need to be "libedit.so.3"?
—Marco
next prev parent reply other threads:[~2018-07-15 10:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-14 18:44 racket patch not found Marco van Hulten
2018-07-14 20:38 ` Mark H Weaver
2018-07-15 10:39 ` Marco van Hulten [this message]
2018-07-19 7:09 ` Chris Marusich
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=20180715123937.3d08373a@jasniac.instanton \
--to=marco@hulten.org \
--cc=help-guix@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).