Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: man uses more instead of less when cross built
Date: Sat, 11 Jun 2022 18:08:56 +0200	[thread overview]
Message-ID: <20220611160856.93dU3_WG5xYTPF0CfttjODk6Cf9gcMhRY1Z0lY1SiPk@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: 2425 bytes --]

New comment by classabbyamp on void-packages repository

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

Comment:
`hostmakedepends="less"` solves this

Looks like there are a lot of execution failures on cross:

<details><summary>configure log of mdocml</summary>

```
file config.log: writing...
file configure.local: reading...
tested operating system: Linux -> OSENUM=MANDOC_OS_OTHER
tested aarch64-linux-gnu-gcc -W: tested noop: yes
selected CFLAGS="-fstack-clash-protection -D_FORTIFY_SOURCE=2 -O2 -pipe -march=armv8-a -fcommon  -I/usr/aarch64-linux-gnu/usr/include -fdebug-prefix-map=/builddir/mandoc-1.14.6=."
tested noop-static: yes
selected STATIC="-static"
tested attribute: yes
tested cmsg: yes
tested dirent-namlen: no (execution failed)
tested be32toh: yes
tested be32toh-DSYS_ENDIAN: no (execution failed)
tested EFTYPE: no (execution failed)
tested err: yes
tested getline: yes
tested getsubopt: yes
tested isblank: yes
tested mkdtemp: yes
tested mkstemps: yes
tested nanosleep: yes
tested ntohl: yes
tested O_DIRECTORY: yes
tested PATH_MAX: yes
tested pledge: no (execution failed)
tested sandbox_init: no (execution failed)
tested progname: no (execution failed)
tested reallocarray: yes
tested recallocarray: no (execution failed)
tested recallocarray-D_OPENBSD_SOURCE: no (execution failed)
tested recvmsg: yes
tested rewb-bsd: HAVE_REWB_BSD=0 (manual)
tested rewb-sysv: yes
tested strcasestr: no (execution failed)
tested strcasestr-D_GNU_SOURCE: yes
tested stringlist: no (execution failed)
tested strlcat: no (execution failed)
tested strlcpy: no (execution failed)
tested strndup: yes
tested strptime: no (execution failed)
tested strptime-D_GNU_SOURCE: yes
tested strsep: yes
tested strtonum: no (execution failed)
tested strtonum-D_OPENBSD_SOURCE: no (execution failed)
tested vasprintf: no (execution failed)
tested vasprintf-D_GNU_SOURCE: yes
tested fts-DFTS_COMPARE_CONST: no (execution failed)
tested fts: yes
tested less: yes
selected BINM_PAGER=less
tested less -T: yes
selected UTF8_LOCALE=en_US.utf8
tested wchar-DUTF8_LOCALE="en_US.utf8": no (execution failed)
tested wchar-D_GNU_SOURCE -DUTF8_LOCALE="en_US.utf8": yes
tested ohash: no (execution failed)
tested ohash-lutil: no (execution failed)
selected LDADD="    -lz"
file config.h: written
file Makefile.local: written
```

</details>

  reply	other threads:[~2022-06-11 16:08 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 [this message]
2022-06-13  8:25 ` [ISSUE] [CLOSED] " leahneukirchen

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=20220611160856.93dU3_WG5xYTPF0CfttjODk6Cf9gcMhRY1Z0lY1SiPk@z \
    --to=classabbyamp@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).