From: Bruno Haible <bruno@clisp.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 41037@debbugs.gnu.org
Subject: bug#41037: documentation for application developers?
Date: Sun, 03 May 2020 23:13:46 +0200 [thread overview]
Message-ID: <10121112.yT0VcRYgiK@omega> (raw)
In-Reply-To: <87pnbkvio0.fsf@gnu.org>
Hi Ludo,
> > I would expect to find these issues discussed, at least:
> > - hard-coded program names like /bin/pwd
>
> These should be avoided; it’s not Guix-specific, but the problem is
> obviously more acute here.
/bin/pwd exists on all other Unix systems; so de facto it _is_ Guix
specific.
> > - where is /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 ?
>
> It’s in the glibc package:
>
> ls $(guix build glibc | grep '[0-9]$')/lib
>
> What’s your use case?
So, the consequence is that a Guix user cannot send an executable
to another Guix user and expect it to be runnable on the other machine.
This too is Guix specific; maybe it is already documented?
> > - libtool, ldconfig issues
>
> ‘ldconfig’ is not used. Nothing special for Libtool.
> Do you have something in mind?
I wanted to have background information regarding ldconfig and shared
library caches, in order to investigate bug#41038
<https://lists.gnu.org/archive/html/bug-guix/2020-05/msg00036.html>.
Bruno
next prev parent reply other threads:[~2020-05-03 21:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 23:36 bug#41037: documentation for application developers? Bruno Haible
2020-05-03 20:59 ` Ludovic Courtès
2020-05-03 21:13 ` Bruno Haible [this message]
2020-05-03 21:48 ` Danny Milosavljevic
2020-05-03 22:57 ` Bruno Haible
2020-05-03 22:18 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-05-04 8:18 ` Ludovic Courtès
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=10121112.yT0VcRYgiK@omega \
--to=bruno@clisp.org \
--cc=41037@debbugs.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).