From: dogknowsnx <dogknowsnx@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: findutils: update to 4.10.0
Date: Fri, 01 Aug 2025 23:49:29 +0200 [thread overview]
Message-ID: <20250801214929.B77162936C@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-56575@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1576 bytes --]
New comment by dogknowsnx on void-packages repository
https://github.com/void-linux/void-packages/pull/56575#issuecomment-3145856548
Comment:
Attempting to build without `gnulib-tests`, which fails because `include/error.h` is missing, only available for `libc`:
```
~ ❯ xlocate include/error.h [0] 23:35
cross-aarch64-linux-gnu-libc-0.37_2 /usr/aarch64-linux-gnu/usr/include/error.h
cross-arm-linux-gnueabi-libc-0.37_1 /usr/arm-linux-gnueabi/usr/include/error.h
cross-arm-linux-gnueabihf-libc-0.37_1 /usr/arm-linux-gnueabihf/usr/include/error.h
cross-armv7l-linux-gnueabihf-libc-0.37_1 /usr/armv7l-linux-gnueabihf/usr/include/error.h
cross-i686-pc-linux-gnu-libc-0.37_1 /usr/i686-pc-linux-gnu/usr/include/error.h
cross-i686-w64-mingw32-crt-12.0.0_1 /usr/i686-w64-mingw32/include/error.h
cross-powerpc-linux-gnu-libc-0.37_1 /usr/powerpc-linux-gnu/usr/include/error.h
cross-powerpc64-linux-gnu-libc-0.37_1 /usr/powerpc64-linux-gnu/usr/include/error.h
cross-powerpc64le-linux-gnu-libc-0.37_1 /usr/powerpc64le-linux-gnu/usr/include/error.h
cross-powerpcle-linux-gnu-libc-0.34_1 /usr/powerpcle-linux-gnu/usr/include/error.h
cross-riscv64-linux-gnu-libc-0.37_1 /usr/riscv64-linux-gnu/usr/include/error.h
cross-x86_64-w64-mingw32-crt-12.0.0_1 /usr/x86_64-w64-mingw32/include/error.h
cross-x86_64-w64-mingw32ucrt-crt-12.0.0_1 /usr/x86_64-w64-mingw32ucrt/include/error.h
glibc-devel-2.41_1 /usr/include/error.h
```
next prev parent reply other threads:[~2025-08-01 21:49 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-01 15:21 [PR PATCH] " dogknowsnx
2025-08-01 15:26 ` [PR PATCH] [Updated] " dogknowsnx
2025-08-01 15:34 ` dogknowsnx
2025-08-01 15:39 ` dogknowsnx
2025-08-01 15:45 ` dogknowsnx
2025-08-01 15:49 ` dogknowsnx
2025-08-01 15:53 ` dogknowsnx
2025-08-01 16:04 ` [PR REVIEW] " Duncaen
2025-08-01 16:05 ` [PR PATCH] [Updated] " dogknowsnx
2025-08-01 16:09 ` Duncaen
2025-08-01 16:27 ` [PR PATCH] [Updated] " dogknowsnx
2025-08-01 16:33 ` dogknowsnx
2025-08-01 16:36 ` [PR REVIEW] " Duncaen
2025-08-01 16:37 ` Duncaen
2025-08-01 16:38 ` [PR REVIEW] " dogknowsnx
2025-08-01 16:40 ` dogknowsnx
2025-08-01 16:42 ` [PR PATCH] [Updated] " dogknowsnx
2025-08-01 17:57 ` [PR REVIEW] " dogknowsnx
2025-08-01 17:59 ` dogknowsnx
2025-08-01 18:01 ` dogknowsnx
2025-08-01 18:41 ` Duncaen
2025-08-01 18:44 ` Duncaen
2025-08-01 18:44 ` Duncaen
2025-08-01 18:47 ` dogknowsnx
2025-08-01 20:08 ` [PR PATCH] [Updated] " dogknowsnx
2025-08-01 20:21 ` dogknowsnx
2025-08-01 20:36 ` dogknowsnx
2025-08-01 20:41 ` dogknowsnx
2025-08-01 20:46 ` dogknowsnx
2025-08-01 20:51 ` dogknowsnx
2025-08-01 20:59 ` dogknowsnx
2025-08-01 21:11 ` dogknowsnx
2025-08-01 21:24 ` dogknowsnx
2025-08-01 21:40 ` dogknowsnx
2025-08-01 21:49 ` dogknowsnx [this message]
2025-08-01 22:06 ` dogknowsnx
2025-08-01 22:19 ` [PR PATCH] [Updated] " dogknowsnx
2025-08-01 22:23 ` dogknowsnx
2025-08-01 22:25 ` [PR PATCH] [Updated] " dogknowsnx
2025-08-01 23:03 ` [PR REVIEW] " classabbyamp
2025-08-01 23:20 ` [PR PATCH] [Updated] " dogknowsnx
2025-08-01 23:22 ` [PR REVIEW] " dogknowsnx
2025-08-06 21:48 ` [PR PATCH] [Merged]: " Duncaen
-- strict thread matches above, loose matches on Subject: below --
2025-01-22 22:15 [PR PATCH] Findutils Stivux
2025-04-25 2:08 ` findutils: update to 4.10.0 github-actions
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=20250801214929.B77162936C@inbox.vuxu.org \
--to=dogknowsnx@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).