-
Notifications
You must be signed in to change notification settings - Fork 265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aes/aesni-macosx-x86_64.S:890:2: error: invalid instruction mnemonic 'endbr64' #933
Comments
Can you tell us what version of macOS / xcode you're using please? |
Still the same as in #866: |
Same problem here... |
I'm assuming you're both using the release version of 3.8.2? Hmm, will need to figure out how to make this fail in CI, which it isn't. Any thoughts @joshuasing ? We may need to adjust macos builds to be explicit about arch if they're not. |
I see the issue, there was one missed patch in the aesni generator. It seems that the newer toolchains ignore this. |
After the new commits (0d9bb74 and 63635ea), I was still getting errors:
I have to put this line: Perhaps @armdn can chime back in, on whether that line is needed on darwin18.7.0. |
It's expected. There was a patch in the first commit that should help you:
d0d17f8
However, what I accidentally merged and then reverted was just a CI
change and apparently the CI still cannot reprdocue the problem you're
seeing.
|
I'm not sure I follow. Do you mean d0d17f8 was meant to deal with this #933 issue, but the subsequent 96e5e35 removing patches/asm/0005-Revert-aesni-endbr64.patch was deliberate, because the CI still produces no error, therefore d0d17f8 is deemed not necessary in the master branch? commit 96e5e35
commit d0d17f8
|
With latest pulls on master now is everything goes smoothly. Builded just right now. |
@armdn Thanks. Could you check if you have the ./patches/asm/0005-Revert-aesni-endbr64.patch in your build directory after pulling? I don't, which I guess is the problem on my end (not sure it's supposed to be included or not, yet). |
Yep, no such .patch file in this directory. |
@vollkommenheit I have now landed patch 005 in #949. Hopefully that will resolve your issues if you build from HEAD. |
|
For @vollkommenheit and others who may encounter this issue on ancient releases of Mac OS X: I had to build something using the developer tools from Xcode 6.0.1 on macOS 10.9.5 Mavericks. I observed that LibreSSL 3.8.2 and 3.8.3 would not compile, but 3.8.1 and 3.9.0 are OK. So I moved ahead to the 3.9 branch. |
Mind posting the error in 3.8.3? I don't have an ancient machine to test on there, but it should have most of the fixes from 3.9.0. |
I redownloaded the 3.8.3 tarball to make sure and I can confirm the error. I've attached a copy of the output. It looks identical to what vollkommenheit posted above. |
Are you using a newer compiler than that OS shipped with? I tried it on an old vagrant box of 10.9 from 10 years ago, and while I had issues just using any of the basic tools like curl and wget, it seemed to build OK with the ancient stuff. |
I'm using a vanilla setup with only Xcode 6.2 (6C131e) and the Command Line Tools installed.
|
I tested with 3.8.4 and the issue appears to be resolved. |
Thanks a lot @wtn |
Same error as the resolved #866 but now in another file:
Last successful build was 2023-10-21.
The text was updated successfully, but these errors were encountered: