From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gnucobol: update to 3.2
Date: Fri, 18 Aug 2023 05:10:16 +0200 [thread overview]
Message-ID: <20230818031016.S3ZOGYWPBYF7i4Fz89gxKDZwU_dxkBCMNi72JawMRmc@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: 1149 bytes --]
New comment by cinerea0 on void-packages repository
https://github.com/void-linux/void-packages/pull/45629#issuecomment-1683237764
Comment:
The test cases have been fixed by disabling hardening and defining a custom check step; this will appear in the next push.
I did some investigating and found out what's causing the install failure on cross-compile. Only when cross-compiling, the file `/usr/lib/gnucobol/CBL_OC_DUMP.so` is not generated, this is what gets moved over in that second `vmove` line. Is this file necessary for gnucobol to function?
EDIT: I found the lines that may be causing this, but I'm not sure how to fix it. From `configure.ac`:
```
# Generate the output
AM_CONDITIONAL([COB_MAKE_IX], [test "$COB_HAS_ISAM" != no])
AM_CONDITIONAL([COB_MAKE_RUN_BINARIES], [test "$cross_compiling" != yes])
dnl FIXME: Should be tested as the system may can actually run these
dnl for example x86/x64 cross, GNU/Linux with Wine, Bash on Windows, ...
```
From `extras/Makefile.am` (where `CBL_OC_DUMP.so` would be compiled):
```
if COB_MAKE_RUN_BINARIES
extras_DATA = CBL_OC_DUMP.$(COB_MODULE_EXT)
endif
```
next prev parent reply other threads:[~2023-08-18 3:10 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 [this message]
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
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=20230818031016.S3ZOGYWPBYF7i4Fz89gxKDZwU_dxkBCMNi72JawMRmc@z \
--to=cinerea0@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).