-
Notifications
You must be signed in to change notification settings - Fork 19
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
fix CI on MacOS #50
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As we now have the CI providing the necessary files we get the testsuite.log from the failing MacOS worker from https://github.com/OCamlPro/gnucobol/suites/7271491263/artifacts/292665789 - as this will go away some day here is the file from the last run: testsuite.log.
checking the details we end up with system setting issues:
So while "cobc" runs with the correct libcob loaded (not unlikely only because the libtool generated wrapper) the programs started by cobc do not. The intention is that atlocal, which is sourced by the testsuite and therefore is exported from the environment that starts the programs (cobc in this case) does the necessary setup of all path configurations (which is also included in the testsuite log):
Rechecking shows that MacOS disabled DYLD_LIBRARY_PATH per default via security policy (= this will only work on old systems or if explicit disabled), and the only option to execute the not yet installed libcob is to add an explicit RPATH entry for its path.
I've tried to do so with #49, if it works out the tests should likely all pass on that worker, too and I'll push that upstream (it still feels hacky, if you have any idea what to check "more" to enable/disable this hack I'd welcome any review comments.
The text was updated successfully, but these errors were encountered: