From: klarasm <klarasm@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: bird: update to 2.0.8
Date: Mon, 29 Mar 2021 02:54:05 +0200 [thread overview]
Message-ID: <20210329005405.J-a0Y9xZ8eVu4U3Ddb7gw2RwSQihiZrtwjeDO6PG9mc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29839@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1710 bytes --]
New comment by klarasm on void-packages repository
https://github.com/void-linux/void-packages/pull/29839#issuecomment-808997947
Comment:
It seems that the build fails on x86_64-musl with `XBPS_CHECK_PKGS=yes`. I have replicated this on my machine. Attaching logs from builds with and without checks. I have not noticed any problems yet, but my use of the package may not trigger it.
I have located the error in the check to the following tests in lib/printf_test.c:
```
/* These tests fail.
* from man 3 printf:
* m (Glibc extension; supported by uClibc and musl.) Print output of strerror(er‐
* rno). No argument is required.
* Maybe libc problem?
errno = 5;
BSPRINTF(18, "Input/output error", buf, "%m");
*/
/* printf("%m\n\0", buf);
* outputs "I/O error" instead
*/
/*
errno = 0;
BSPRINTF(18, "Input/output error", buf, "%M", 5);
*/
/*
* printf("%M\n\0", buf);
* does not seem to output anything
*/
```
Anyway, the tests that do not pass don't seem very critical to the function of the package. If it's a libc issue it's a bit weird that it only manifests on x86_64 and none of the arm archs.
From musl-1.1.24 src/errno/__strerror.h:39
`E(EIO, "I/O error")`
From man 3 errno
` EIO Input/output error (POSIX.1-2001).`
[bird-v2.0.8_build.log](https://github.com/void-linux/void-packages/files/6218463/bird-v2.0.8_build.log)
[bird-v2.0.8_build-with-checks.log](https://github.com/void-linux/void-packages/files/6218464/bird-v2.0.8_build-with-checks.log)
[printf_test.c.txt](https://github.com/void-linux/void-packages/files/6218550/printf_test.c.txt)
next prev parent reply other threads:[~2021-03-29 0:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 23:46 [PR PATCH] " klarasm
2021-03-29 0:54 ` klarasm [this message]
2021-03-29 1:29 ` ericonr
2021-03-29 18:23 ` ericonr
2021-03-29 18:36 ` ericonr
2021-03-29 18:43 ` ericonr
2021-03-29 19:12 ` [PR PATCH] [Updated] " klarasm
2021-03-29 19:22 ` klarasm
2021-03-29 19:58 ` [PR PATCH] [Merged]: " ericonr
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=20210329005405.J-a0Y9xZ8eVu4U3Ddb7gw2RwSQihiZrtwjeDO6PG9mc@z \
--to=klarasm@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).