Build error met-10.1.1.20220419 on macOS Monterey 12.1 / apple-clang 13.1.6 / homebrew Python 3.9 / spack #1762
-
Describe the ProblemTrying to build met-10.1.1.20220419 on macOS Monterey 12.1 with apple-clang 13.1.6, homebrew Python 3.9 using spack-stack (https://github.com/noaa-emc/spack-stack) in Rosetta2 emulator mode for
I don't see from that lengthy command where the macOS Python framework is coming in, all I see is multiple occurrences of I searched for similar errors on the web, and noticed that there wasn't a lot of information out there, and what I could find didn't really explain why it's trying to use the Apple SDK when Python is actually coming from homebrew. Just wondering if any of the MET developers have come across this issue by coincidence. Note. MET builds fine in our GitHub actions CI tests, where we also have macOS builds. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 9 replies
-
Hi @climbfuji! I see you created an issue in the MET repository about this compilation question. I transferred it over to the METplus repo and converted it to a discussion in the Installation category. We handle Q&A for all of the METplus components, including MET itself, in the single METplus discussions instance, rather than having separate discussion areas for each component. I hope you're settling in well at JCSDA and hope there's some potential for the use of METplus there! @jprestop is the person with the most experience compiling MET on a variety of platforms, so she's a great resource. Although I can confirm that I routinely compile MET during development on my own Mac laptop and don't experience this error. And I haven't heard of this issue from any other users or developers. Some Googling led me to Stack Overflow and I thought this comment looked informative. There may be some system setting that's triggering this error. Checking my own settings though, you'll see that I'm configured in a very similar way:
I believe I installed this using MacPorts rather than Homebrew. But one big difference is that I am NOT compiling with clang. Instead, I'm using GNU:
And that was also installed via MacPorts ( @jprestop I wonder if perhaps @prestopUCAR has compiled MET with python embedding support using clang via CLion? |
Beta Was this translation helpful? Give feedback.
-
Sorry, no. I did not have my mac or CLion back when I was doing MET development. |
Beta Was this translation helpful? Give feedback.
-
@jprestop @JohnHalleyGotway I finally got to work on this and found the reason and a solution. It had to do with how spack/spack#33409 The same commits are used in our spack fork: |
Beta Was this translation helpful? Give feedback.
@jprestop @JohnHalleyGotway I finally got to work on this and found the reason and a solution. It had to do with how
spack
defined the shared Python library. The issue and pull request for the authoritative spack repository are:spack/spack#33409
spack/spack#33410
The same commits are used in our spack fork:
JCSDA/spack-stack#316
JCSDA/spack#185