From: William Hu <purplearmadillo77@proton.me>
To: Jon Turney <jon.turney@dronecode.org.uk>
Cc: David Allsopp <David.Allsopp@cl.cam.ac.uk>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITA] ocaml 4.14.0
Date: Sat, 23 Jul 2022 16:38:47 +0000 [thread overview]
Message-ID: <w_fh4uOhNWsdqXUi4cRFeZc8LjegTjoa8pw77dVAXCntYVLsTjrDuEoE4hX6BfbKVRLY_-G8-wCmxs_qTBBnBZ1EqaEwMGFbGIAqf3hBDtQ=@proton.me> (raw)
In-Reply-To: <ad3816cb-6ddd-c8d8-0b91-9722f1ba351f@dronecode.org.uk>
>
> Yeah, that seems plausible, but I'm not clear why we are seeing
> different behaviour...
>
After a long period of poking around for differences, I think I found the error - I had the `noacl` option activated in /etc/fstab which was preventing chmod and executable bits from working properly. Removing noacl and rebuilding fixed the problem (no more exe suffixes!)
More fixes:
- The failing tests about address spaces were resolved when I upgraded to flexdll 0.39.
- The failing tests about unused variables are patched
- Shared runtime removed as per above
As far as I know, I think this is everything resolved for 64-bit. The package passes all tests and runs on a few simple files when installed through an overlay. I've uploaded the 64-bit version as a test package.
Thanks,
William
next prev parent reply other threads:[~2022-07-23 16:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 2:03 William Hu
2022-07-04 17:03 ` Jon Turney
2022-07-05 0:42 ` William Hu
2022-07-05 19:44 ` Jon Turney
2022-07-13 2:56 ` William Hu
2022-07-13 15:41 ` David Allsopp
2022-07-14 3:36 ` William Hu
2022-07-14 14:56 ` David Allsopp
2022-07-15 3:20 ` William Hu
2022-07-16 14:22 ` Jon Turney
2022-07-23 16:38 ` William Hu [this message]
2022-07-31 14:52 ` Jon Turney
2022-08-07 2:26 ` William Hu
2022-08-23 20:00 ` David Allsopp
2022-08-24 9:20 ` Corinna Vinschen
2022-08-24 9:28 ` David Allsopp
2022-08-24 9:28 ` David Allsopp
2022-08-24 10:04 ` Corinna Vinschen
2022-07-16 14:05 ` Jon Turney
2022-07-17 20:56 ` William Hu
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='w_fh4uOhNWsdqXUi4cRFeZc8LjegTjoa8pw77dVAXCntYVLsTjrDuEoE4hX6BfbKVRLY_-G8-wCmxs_qTBBnBZ1EqaEwMGFbGIAqf3hBDtQ=@proton.me' \
--to=purplearmadillo77@proton.me \
--cc=David.Allsopp@cl.cam.ac.uk \
--cc=cygwin-apps@cygwin.com \
--cc=jon.turney@dronecode.org.uk \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).