-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
gfortran binaries installed by meson have rpath problem #10711
Comments
@rgommers did people experience similar problems with scipy? |
Not that I know of (yet). But both in CI and in most people's dev setups, the |
That might be the reason why you don't hit that. |
One related issue I just had is that For the purposes of this issue, it would be useful if you could show the |
This is what I'm seeing on my Mac with "otool -l ./mf6" after a meson install:
This is what is shown with "otool -l ./mf6" when I run it in the builddir
Compiler is:
The meson installed version of the binary gives:
The binary created in the build directory works just fine, so it is in the "install" that is stripping off some load commands. My apologies if I'm doing something wrong here, which could very well be the case. I'm running on macOS Monterey version 12.6. |
I've tried this with I also tried building SciPy with Homebrew gcc 12.2, but that doesn't work - for some reason the Homebrew compilers are unable to find the C++ standard library. Building with conda-forge Clang + Homebrew gfortran works fine.
That looks wrong indeed. I cannot reproduce that with Meson 0.63.3 - I'm getting an absolute path:
|
Describe the bug
gfortran seems to have changed the way the way RPATH is handled on Mac as described here. When we use the latest versions of gfortran installed with Homebrew and Macports, the binaries "installed" by Meson fail to run and return
The original binaries created by meson prior to being "installed" work just fine, and so it appears there is an RPATH issue that arises during the meson "install" process.
To Reproduce
This occurs when building MODFLOW here. We haven't seen the issue yet on Github actions, presumably because we are using an older version of gfortran. It appears that the RPATH change is being back ported to earlier version of gfortran; we've seen issues with both gfortran 11.3 and 12.1.
system parameters
meson --version
is 0.63.1ninja --version
is 1.10.2.git.kitware.jobserver-1Other MODFLOW team members affected include @Hofer-Julian and @w-bonelli
The text was updated successfully, but these errors were encountered: