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

pgplot vs brew (MACOS) #175

Open
jcldc opened this issue Feb 19, 2025 · 15 comments
Open

pgplot vs brew (MACOS) #175

jcldc opened this issue Feb 19, 2025 · 15 comments

Comments

@jcldc
Copy link
Collaborator

jcldc commented Feb 19, 2025

Here is a way to install pgplot via brew installer on macos computer :

brew install kazuakiyama/pgplot/pgplot
@teuben
Copy link
Owner

teuben commented Feb 19, 2025

that's great news. The claim from official brew was that pesky caltech licencing lawyer

@teuben
Copy link
Owner

teuben commented Feb 19, 2025

well, brew installed a lot, including pgplot. configure then found it. the install completely broken, there's bizarry clang error messages, indicating a conflict between my brew based gcc, and the system clang. I switched to "--enable-clang", which fared better. Still some errors for which I'll have to come back to later.

@jcldc
Copy link
Collaborator Author

jcldc commented Feb 20, 2025

Well, I have clang configured by default (on my M4 mac mini), and the installation went flawlessly for me.

@teuben
Copy link
Owner

teuben commented Feb 20, 2025

Is your gyrfalcON working now?

@jcldc
Copy link
Collaborator Author

jcldc commented Feb 20, 2025

Yes It's working fine !
I have recompiled NEMO (+falcON) using clang. It's mandatory if I want to use nemolib + falconlib in a python module (on a MAC). This is why I had to install pgplot using brew install ... .
I am struggling with @rpath stuffs too, by the way.
I am porting my codes, unsio, unsiotools on MAC ARM, it's challenging, especially the python part. I switched from setup.py to pyproject.toml for the python module building.

@teuben
Copy link
Owner

teuben commented Feb 20, 2025

You did not run into the missing mm_malloc.h file ? (#173 )

But currently if you would run "make bench5" it should crash because of SIP (#174 )

@jcldc
Copy link
Collaborator Author

jcldc commented Feb 20, 2025

Nope, I did not run into the missing mm_malloc.h file because of this statement which exclude clang compiler:

#if defined(__GNUC__) && !defined(__INTEL_COMPILER)
#  include <mm_malloc.h>
#endif

But, yes make bench5 failed miserably too...

@teuben
Copy link
Owner

teuben commented Feb 20, 2025

For bench5 we have 2 solutions as you saw: rpath compiling, or ensuring DYLD_LIBRARY_PATH is present again, which I can do in a fix to the script ( I thought )

@teuben
Copy link
Owner

teuben commented Feb 20, 2025

I also wrote a macron, sorry, macrun script, which sets DYLD_LIBRARY_PATH if it's not present. It does assume $NEMO is present, so it just sources the nemo_start.sh file. what a mess.

@jcldc
Copy link
Collaborator Author

jcldc commented Feb 20, 2025

Crazy things !!
It's actually /usr/bin/time command which make crash gyrfalcON.

Try from a terminal (NEMO loaded) the followings commands :

time gyrfalcON

and

/usr/bin/time gyrfalcON

The latter crashes gyrfalcoN !!!

@jcldc
Copy link
Collaborator Author

jcldc commented Feb 20, 2025

/usr/bin/time starts a sub process. It must be the reason DYD_LD_LIBRARY_PATH is cleared.

@teuben
Copy link
Owner

teuben commented Feb 20, 2025

ah thanks, I'll fix that tonight when I can dig up that mac !
I still will have problems with "make check", there I need macron!

@teuben
Copy link
Owner

teuben commented Feb 20, 2025

or maybe I should call it "siprun"

@jcldc
Copy link
Collaborator Author

jcldc commented Feb 20, 2025

ah thanks, I'll fix that tonight when I can dig up that mac ! I still will have problems with "make check", there I need macron!

macron ? Emmanuel ? Our French president ?

@teuben
Copy link
Owner

teuben commented Feb 20, 2025

yup, that guy. I won't make a decision until later when I get home.

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

No branches or pull requests

2 participants