-
Notifications
You must be signed in to change notification settings - Fork 145
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
[MacOS] Avrdude built using autotools doesn't work #1884
Comments
libelf depreciation in MacOS? |
I do have libelf installed. And the binary works if I build using build.sh |
The A simple test for this hypothesis would be to call |
I tried running
But I'm still getting the exact same error when running |
Your steps are wrong. The right steps are as following.
If I follow your step, I can see the following configuration summary output.
Using my steps, here is the output.
|
Wiki updated. @MCUdude |
That doesn't fix the issue:
|
... But I think this warning is new:
The |
Hmm, it seems to me your Homebrew installation is broken... I have no issues on my side. Anyway, I have re-opened the issue. |
The CI ˋbuild.ymlˋ tests (macos, msvc, mingw) should probably test that the ˋavrdudeˋ executable` which they have just built actually runs. The native linux builds (both cmake and automake) run the ˋDryrun_testˋ stage which should check that by running ˋ./tools/test-avrdudeˋ. Hmmm.... now that I take a look at the output for the non-cmake case, I am not sure that stage actually runs `avrdudeˋ. The script does not fail, though. I guess I should make certain that the Then I can hopefully reproduce the linking issue on the macos CI builds, and then try to fix it. Plan B: Ask a friend to borrow his Mac for a bit. |
@ndim Great plan A.
Pro tip: use the
|
We don't have to resolve this before the 8.0 release. I'm currently building using CMmake, and I'm prioritizing testing various programmers and targets. There have been quite a few regressions discovered in the JTAG3 code base, and I hope we're able to iron all these out. |
This could be a consequence of removing the static If formerly static linking worked and now dynamic linking fails.... That could be it. Is the homebrew libelf library existing as both shared/dynamic and static, by chance? |
How do I check this? BTW I just tried building PR #1888 using
|
On the GitHub macos worker,
So |
OK... let's continue this after 8.0 with finding out how the homebrew on @MCUdude's mac differs from the github worker ( If we are lucky, just switching to using pkg-config for finding all dependencies which provide a |
As mentioned, I do not have issues with my Mac Mini M1 with Homebrew (both Apple Silicon and x86_64). I tend to think @MCUdude's homebrew installation is broken... Maybe there are permission problems of sub-directories under '/opt/homebrew', say
Please help to post the output of the following command. Thanks.
|
|
Can you try the following configure option to be in line with
|
Here is my build log under macOS.
|
The produced binay is also working.
|
BTW, homebrew formular may need a bit of change if they want the Python bindings to be installed. Somehow it does not work under my system.
|
This issue has not been resolved. The automatic closing of this issue is an unintended byproduct of the automation. Could someone with enough karma points reopen this? |
Please help to try again to see if you still have issues or not. I can not reproduct the issue and I actually believe it is more of a problem of your macOS system. |
This regression must have been introduced recently. When building Avrdude using
./bootstrap && ./configure && make
, I'm getting this error when trying the execute the binary:Not sure what's causing this. Do you have any idea @stefanrueger or @ndim?
The text was updated successfully, but these errors were encountered: