Skip to content
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

Failing to build on Rocky 8 #395

Closed
williameveretteggplant opened this issue Apr 26, 2024 · 3 comments
Closed

Failing to build on Rocky 8 #395

williameveretteggplant opened this issue Apr 26, 2024 · 3 comments

Comments

@williameveretteggplant
Copy link
Contributor

Starting with commit: 4515e4a
libs-base is failing to build on Rocky 8 with this message:
checking FFI library usage... configure: error: The ffi library (libffi) does not appear to be working. Perhaps it's missing or you need a more recent version. Version 3.0.9 or later should work, and you can find a link to it n the list of packages for download at http://www.gnustep.org/resources/sources.html
I can confirm that does build on Ubuntu 22.
Now, Rocky 8 only has libffi 3.1, while Ubuntu 22 has libffi 3.5. But 3.1 should be sufficient. Also, this message could be red herring, hiding another reason.
Does anybody know what is going on?

@gcasa
Copy link
Member

gcasa commented Apr 26, 2024

Starting with commit: 4515e4a

libs-base is failing to build on Rocky 8 with this message:

checking FFI library usage... configure: error: The ffi library (libffi) does not appear to be working. Perhaps it's missing or you need a more recent version. Version 3.0.9 or later should work, and you can find a link to it n the list of packages for download at http://www.gnustep.org/resources/sources.html

I can confirm that does build on Ubuntu 22.

Now, Rocky 8 only has libffi 3.1, while Ubuntu 22 has libffi 3.5. But 3.1 should be sufficient. Also, this message could be red herring, hiding another reason.

Does anybody know what is going on?

This could be due to whatever path libffi is located at not being present in the LD_LIBRARY_PATH at build time.

@williameveretteggplant
Copy link
Contributor Author

It looks like @qmfrederik is already looking into this...

@qmfrederik
Copy link
Contributor

Yes, the culprit is 4515e4a; has a #389 fix but I believe @rfm wanted to have a closer look at this. @williameveretteggplant if you cherry-pick e0af8f8 it should unblock you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants