Github messages for voidlinux
 help / color / mirror / Atom feed
From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] man uses more instead of less when cross built
Date: Mon, 13 Jun 2022 10:25:35 +0200	[thread overview]
Message-ID: <20220613082535.IGOjqmxNdJJfCAh6YLfT30jLLn_PmHkdjmavCYiPSsI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37512@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1695 bytes --]

Closed issue by lfdebrux on void-packages repository

https://github.com/void-linux/void-packages/issues/37512

Description:
<!-- Don't request update of package. We have a script for that. https://repo-default.voidlinux.org/void-updates/void-updates.txt. However, a quality pull request may help. -->
### System

* xuname: Void 5.15.41_1 x86_64-musl GenuineIntel notuptodate rFFFF

* package:  mdocml-1.14.6_3

### Expected behavior

`man` uses `less` as the default pager. (The mdocml package has less as a dependency so less should always be installed with man on a Void Linux system)

### Actual behavior

`man` uses `more` as the default pager.

### Steps to reproduce the behavior

- check out latest version of void-packages repo
- crossbuild mdocml (for instance with `./xbps-src -a armv5tel-musl pkg mdocml`
- install mdocml on target device
- open a man page (for instance `man man`)

### Notes

I think this happens because although less is a build dependency of mdocml, the configure script for mandoc tries to run less to check whether it is present, but the cross version gets installed in `usr/arm-linux-musleabi/bin`, which isn't in PATH (and probably wouldn't run anyway being a non-native binary).

I figured out what was going on by running `xbps-src -a armv5tel-musl configure mdocml`, and looking at `masterdir/builddir/mandoc*/config.log`. I also verified that the same thing happened when cross-compiling for different targets (and different architectures).

I'm not sure of the right way to fix this, setting `BINM_PAGER` in `configure.local` would probably do the job, but maybe there is a more standard way of fixing this sort of problem?


      parent reply	other threads:[~2022-06-13  8:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-11 11:17 [ISSUE] " lfdebrux
2022-06-11 16:08 ` classabbyamp
2022-06-13  8:25 ` leahneukirchen [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220613082535.IGOjqmxNdJJfCAh6YLfT30jLLn_PmHkdjmavCYiPSsI@z \
    --to=leahneukirchen@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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 NNTP newsgroup(s).