From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Ludovic Courtès" <ludo@gnu.org>, "Pierre Neidhardt" <mail@ambrevar.xyz>
Cc: 30785@debbugs.gnu.org
Subject: bug#30785: Man pages truncated, repeated
Date: Mon, 14 Jan 2019 22:42:49 +0100 [thread overview]
Message-ID: <20190114224249.6bd4452f@scratchpost.org> (raw)
In-Reply-To: <874labq91k.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1257 bytes --]
Hi Pierre,
Hi Ludo,
On Mon, 14 Jan 2019 21:27:35 +0100
Ludovic Courtès <ludo@gnu.org> wrote:
> The ‘set_current_prefix’ logic is extremely fragile; it should readlink
> from /proc/self/exe on GNU/Linux.
>
> But in our case, no relocation happens, so we can just patch it to do:
>
> void set_current_prefix (void)
> {
> curr_prefix = "/gnu/store/…";
> }
I agree.
However, in this case the question is why is it picking up all that stuff anyway.
The relocation is only used in the case of the groff-local localcharset.c being
used.
It's only a fallback that is used if glibc < 2.1. I've checked the guix build
logs, the glibc version is newer and also found by the 'configure phase of groff.
I can't tell about groff-minimal because the build log as given by
"guix build --log-file groff-minimal"
(https://ci.guix.info/log/mpjn4jfx5i8jxblfj538n22hv56rdnhw-groff-minimal-1.22.3)
has 0 Bytes.
Anyway, a simple way to disable this weird relocation business would be to remove:
./src/libs/libgroff/Makefile.sub: -DENABLE_RELOCATABLE=1 \
However, it would be preferrable to find out why ./src/libs/gnulib/lib/localcharset.c
(the only user of it) is used at all. It really shouldn't be.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-01-14 21:43 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 21:24 bug#30785: Man pages truncated, repeated Tobias Geerinckx-Rice
2018-03-13 21:34 ` Ludovic Courtès
2018-03-13 22:01 ` Tobias Geerinckx-Rice
2018-03-14 13:22 ` Ludovic Courtès
2018-03-14 13:43 ` Andreas Enge
2018-03-15 0:40 ` Marius Bakke
2018-05-05 21:40 ` Marius Bakke
2018-05-06 13:53 ` Marius Bakke
2018-05-06 22:06 ` Marius Bakke
2018-05-05 1:31 ` Vagrant Cascadian
2018-08-20 10:32 ` Pierre Neidhardt
2019-01-13 16:09 ` Pierre Neidhardt
2019-01-13 16:15 ` Pierre Neidhardt
2019-01-13 17:00 ` Ludovic Courtès
2019-01-13 17:31 ` Pierre Neidhardt
2019-01-13 17:43 ` Pierre Neidhardt
2019-01-13 20:27 ` Ludovic Courtès
2019-01-13 20:37 ` Pierre Neidhardt
2019-01-14 8:36 ` Ludovic Courtès
2019-01-14 8:49 ` Pierre Neidhardt
2019-01-14 10:19 ` Pierre Neidhardt
2019-01-14 10:59 ` Gábor Boskovits
2019-01-14 15:06 ` Pierre Neidhardt
2019-01-14 16:10 ` Ludovic Courtès
2019-01-14 16:24 ` Pierre Neidhardt
2019-01-14 16:42 ` Danny Milosavljevic
2019-01-14 16:57 ` Pierre Neidhardt
2019-01-14 17:46 ` Danny Milosavljevic
2019-01-14 17:48 ` Danny Milosavljevic
2019-01-14 17:50 ` Danny Milosavljevic
2019-01-14 18:19 ` Pierre Neidhardt
2019-01-14 20:27 ` Ludovic Courtès
2019-01-14 21:42 ` Danny Milosavljevic [this message]
2019-01-14 21:59 ` Pierre Neidhardt
2019-01-14 22:14 ` Danny Milosavljevic
2019-01-14 22:39 ` Pierre Neidhardt
2019-01-15 12:29 ` Ludovic Courtès
2019-01-16 10:01 ` Pierre Neidhardt
2019-01-16 10:56 ` Danny Milosavljevic
2019-01-16 13:02 ` Pierre Neidhardt
2019-01-16 14:17 ` Danny Milosavljevic
2019-01-16 17:39 ` Pierre Neidhardt
2019-01-16 18:12 ` Efraim Flashner
2019-01-16 18:18 ` Pierre Neidhardt
2019-01-16 19:57 ` Danny Milosavljevic
2019-01-16 22:32 ` Ludovic Courtès
2019-01-16 22:45 ` Danny Milosavljevic
2019-01-17 7:31 ` Pierre Neidhardt
2019-01-17 8:43 ` Ludovic Courtès
2019-01-17 9:39 ` Pierre Neidhardt
2019-01-17 9:42 ` Pierre Neidhardt
2019-01-17 11:32 ` Pierre Neidhardt
2019-11-28 0:13 ` Marius Bakke
2019-01-17 9:10 ` Danny Milosavljevic
2019-01-17 8:33 ` Ludovic Courtès
2019-01-17 8:41 ` Pierre Neidhardt
2021-04-22 18:53 ` G. Branden Robinson
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=20190114224249.6bd4452f@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=30785@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=mail@ambrevar.xyz \
/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).