From: GitMensch <GitMensch@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gnucobol: update to 3.2
Date: Wed, 23 Aug 2023 09:00:51 +0200 [thread overview]
Message-ID: <20230823070051.UNbBUAXyJsseGz-3Uzuav2pTREcRzr-EUVJGE4UhWPM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45629@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 917 bytes --]
New comment by GitMensch on void-packages repository
https://github.com/void-linux/void-packages/pull/45629#issuecomment-1689292116
Comment:
The currently failing test 488 on musl is a bug "not clean handling" in GnuCOBOL. You may want to use the official (not yet upstream) patch found in https://git.adelielinux.org/adelie/packages/-/commit/21fe3ef399c25f030d6657e83cc635335f3a9f40 (0002-errno) [and may also take a fix for a regression (0001-move) live].
The failing in test 818 on musl is "known" from the Adélie CI; the issue is that musl _never_ unloads "by design":
https://wiki.musl-libc.org/functional-differences-from-glibc.html#Unloading_libraries
libcob likely _can_ work around this, but that's likely a bunch of work. That issue is tracked upstream as https://sourceforge.net/p/gnucobol/bugs/906/.
You may consider to drop that test for now by running `sed -i tests/testsuite -e "/^818;/d";`
next prev parent reply other threads:[~2023-08-23 7:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 2:50 [PR PATCH] " cinerea0
2023-08-17 3:17 ` [PR PATCH] [Updated] " cinerea0
2023-08-17 3:28 ` cinerea0
2023-08-17 20:03 ` GitMensch
2023-08-17 20:39 ` cinerea0
2023-08-17 20:42 ` GitMensch
2023-08-18 2:23 ` cinerea0
2023-08-18 3:10 ` cinerea0
2023-08-18 5:14 ` GitMensch
2023-08-22 23:24 ` [PR PATCH] [Updated] " cinerea0
2023-08-22 23:26 ` cinerea0
2023-08-23 5:12 ` GitMensch
2023-08-23 5:35 ` GitMensch
2023-08-23 7:00 ` GitMensch [this message]
2023-08-25 5:24 ` GitMensch
2023-08-26 18:02 ` [PR PATCH] [Updated] " cinerea0
2023-09-23 13:32 ` [PR PATCH] [Merged]: " Duncaen
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=20230823070051.UNbBUAXyJsseGz-3Uzuav2pTREcRzr-EUVJGE4UhWPM@z \
--to=gitmensch@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).