Could some macOS users test the installer for the v8.12
branch that can be downloaded from this page? https://dev.azure.com/coq/coq/_build/results?buildId=10328&view=artifacts&type=publishedArtifacts
Usual things to check in CoqIDE (from the top of my head):
I remember doing similar tests for Windows for 8.11.0 and struggling to figure out all the actions that should be tried. Maybe make an issue about writing this down somewhere?
in particular, I think one should test opening a file in the middle of a nontrivial compiled third-party project (to see that _CoqProject
, or equivalent when compiled by dune works)
@Hugo Herbelin has been testing quite a few packages in the past, maybe he would be interested.
It does not work. I have a "dyld: Symbol not found: _NSPasteboardTypeURL" error when running coqide (but coqtop works). No time to investigate now. Full message is:
dyld: Symbol not found: _NSPasteboardTypeURL
Referenced from: /Applications/CoqIDE_8.12+alpha.app/Contents/MacOS/../Resources/lib/libgdk-3.0.dylib
Expected in: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
in /Applications/CoqIDE_8.12+alpha.app/Contents/MacOS/../Resources/lib/libgdk-3.0.dylib
Trace/BPT trap
Thanks a lot for testing Hugo, what's your OSX version @Hugo Herbelin
10.11.1
10.11 is 5 years old. I don't know which versions you want to target. Here, the code is produced using Azure's 10.14 (iiuc), which apparently produces a different format of executable (or, most probably, a format with new features). Maybe adding export MACOSX_DEPLOYMENT_TARGET=10.11
in the Azure script may help (or the same with whatever "deployment" version you want to target).
This variable is already set: https://github.com/coq/coq/blob/3080a8e9500b854344b3df5840feefd15ef0cbd1/azure-pipelines.yml#L56
It is quite surprising that this installer is not working for you but the one for v8.11
that you tested relatively recently was working (after this variable was set).
Oh actually, this variable was not added very recently (coq/coq#10186).
But still, I'm puzzled by this.
lablgtk versions are the same right?
The only difference between v8.11
and v8.12
in the Azure pipeline packaging job is:
@@ -87,6 +98,7 @@ jobs:
- script: |
eval $(opam env)
+ export OCAMLPATH=$(pwd):"$OCAMLPATH"
make -j "$NJOBS" test-suite PRINT_LOGS=1
displayName: 'Run Coq Test Suite'
Bizarre :S
Homebrew is pinned. The macOS image is fixed.
The OCaml and findlib versions are pinned but not the version of lablgtk!
Yup we should try to see if there is a difference in gtk / lablgtk
lablgtk 3.1.0 was released end of January 2020. If the macOS installer for Coq 8.11.1 works on @Hugo Herbelin's machine, then that's not it.
Could be the case that 8.12 is using some more features, for example in the completion. IMHO anyways we should ping.
But yeah, we need someone else to try the package
I tried the actions mentioned by @Théo Zimmermann. It worked for me on macOS 10.15.4 "Catalina".
macOS complained about missing signature before opening CoqIDE, though.
Yeah, that's normal.
Théo Zimmermann said:
lablgtk 3.1.0 was released end of January 2020. If the macOS installer for Coq 8.11.1 works on Hugo Herbelin's machine, then that's not it.
Actually, 8.11.1 does not work either (same error).
Oh OK, and does 8.11.0 work for you? (It was released after the 3.1.0 release but very likely built before.)
The dmg for 8.11.0 works. Note that it does not have the same libgdk-3.0.dylib as in 8.11.1 and that this file does not mention the _NSPasteboardTypeURL
symbol for 8.11.0. (It mentions instead a symbol called _NSURLPboardType
which is apparently deprecated since MacOS 10.14.) Sorry no time for further investigations at the moment.
What (only) matters is probably the version of gtk installed on the Azure pipeline (apparently gtk+3-3.24.11.mojave.bottle.tar.gz according to recent builds) which is not anymore compatible with MacOS 10.11.1 and suspectingly not compatible with 10.12 either, based on the fact that _NSPasteboardTypeURL
arrived in 10.13. Is there a way to know what version of gtk was installed on the Azure pipeline at the time of 8.11.0 for comparison? (In any case, there is no bug involved)
The macOS image was upgraded from macOS-10.13
to macOS-10.14
between 8.11.0 and 8.11.1. So I think this can explain the change of version of gtk+.
Is it a good idea to do it in a minor release, though? Isn't it under our control?
This was coq/coq#11803. Apparently the previous image was deprecated and scheduled to be removed just 12 days after. So no choice but to backport.
But the PR was thoroughly tested. Initially it broke macOS 10.11.1 and then a later version fixed it.
So since then something else must have changed to make it break again.
The release candidate for 8.12.0 is 558e8ea
. If some macOS users are around, it would be great if you could test the generated macOS installer from https://dev.azure.com/coq/coq/_build/results?buildId=11089&view=artifacts&type=publishedArtifacts. Cf. the top of this thread for a list of usual things to check.
Théo Zimmermann said:
The release candidate for 8.12.0 is
558e8ea
. If some macOS users are around, it would be great if you could test the generated macOS installer from https://dev.azure.com/coq/coq/_build/results?buildId=11089&view=artifacts&type=publishedArtifacts. Cf. the top of this thread for a list of usual things to check.
Mojave 10.14.6 here. Almost all actions (open/modify/step/till end/save) seem to work. Query menu doesn't seem to do anything, but in earlier versions of Coq+CodIDE doesn't seem any better for me (never use CoqIDE, so I hardly ever test those things)
For the queries, you should select some text, like "nat" and then Query -> Print
Or hit f1 and there write Print nat
And thanks for testing!
selecting "nat" Query -> Print does do the job. For F1, it clashes with brightness key on Mac keyboard :slight_smile: this is why I never got to use it, I guess (apart from using Aquamacs + PG in general). But after switching keys to standard function keys, it works perfectly fine.
You're welcome! I didn't know that there is such a shortage of Mac testers.
Last updated: Oct 13 2024 at 01:02 UTC