-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
autotools builds not working on apple silicon native #4059
Comments
at least in the conanfile for yasm (here) there is nothing specific to macos, so it seems that |
probably, this is due to the arm64 mis-detection: conan-io/conan#8262 |
Ah, ok, so guess i will need to test with master? |
But does that also fix build arch? My profile seens to require armv8? |
ok, tested, didnt change anything :(. btw, why do i need to manually set the profile? shouldnt conan detect it as default? |
phew, trying to debug, its all rather confusing. as far as I can see it all goes wrong in |
first off: what are target, build, and host os/arch? and to which of these does the plain os/arch settings belong? |
ok, so it seems to work if I hack host/target/build to be the gnu triplet derived from the |
ok, actually iconv still fails, will check more on monday... |
Any update on this? I have trouble with libffi on an M1 chip. Seems like the tripplet is badly recognized as
Before hack:
|
I gave up and we moved to a modified version of cget |
@jmarrec what's your conan profile? what's the output of the following command:
as I understand, after conan-io/conan#8262 it should contain I don't have M1 machine to test, but as far as I can tell, there are several evidences it should compute e.g. both logs contain /cc @a4z @theodelrieu |
I would say, to spot the problem you need to look into the whole configure part, not just one line
because there are packages building with autotools on M1 (have libcurl for example) my guess: the else part from so I do not think that the general statement, that autotools builds not working, can be made |
@SSE4 conan does detect
|
of course it does @jmarrec , but you might need to update your conan installation to a recent version
|
I use 1.34.1. I set up this dev machine last friday, so everything is bleeding edge. |
okay, seems like we have a bug where autotools host/build/arch isn't correctly computed for M1 in some cases. I can't debug it, as I don't have machine, but I can point places where to look.
the easiest way to check if it works:
if you're getting |
|
(I'd like to provide an answer, but I'm having trouble connecting to that remote machine at the moment... sorry) |
no problem, not urgent.
if you have a complete log, it would be nice (e.g. one containing the full command line). |
And I got disconnected by Teamviewer after 30 seconds again... So I can't give a full libffi log. The machine being in another country where everyone is sleeping, there's not much I can do at the moment. I'll try again in 4 hours... What I can say is that I had built libffi by checking out conan-center index, using my default profile above. cd recipes/libffi/all
create create . libffi/3.3@ -b missing |
probably, it might be possible that it's not a conan fault, see libffi/libffi#576 |
That seems pretty spot-on indeed, good sleuthing @SSE4 ! Now is left the question of what conan should do about it?
|
workaround in recipe is okay. you may even explicitly pass |
Package and Environment Details (include every applicable attribute)
Conan profile (output of
conan profile show default
orconan profile show <profile>
if custom profile is in use)Steps to reproduce (Include if Applicable)
require any library built with autotools, like libjpeg, yasm, iconv...
Logs (Include/Attach if Applicable)
Click to expand log
The text was updated successfully, but these errors were encountered: