Thanks, the following worked for me (added missing _). We do use a non-standard location for different mpi versions.
make -j MPI_CC=`which mpicc` MPI_CCC=`which mpic++`
Thanks again for your help.
Search found 5 matches
- 08 May 2025, 08:01
- Forum: Installation
- Topic: 2025.x from source w/ Pelegant
- Replies: 2
- Views: 1236
- 07 May 2025, 14:52
- Forum: Installation
- Topic: 2025.x from source w/ Pelegant
- Replies: 2
- Views: 1236
2025.x from source w/ Pelegant
I've noticed the source for SDDS and elegant recently moved to github. Along with that are some very simple build instructions that indeed work nicely. I was wondering if it would be possible to provide some similarly simple build instructions or guidance for building Pelegant from source. I've been...
- 26 Feb 2025, 09:59
- Forum: Bugs
- Topic: plaindata2sdds
- Replies: 1
- Views: 7359
plaindata2sdds
This may or may not be a follow up to: https://www3.aps.anl.gov/forums/elegant/viewtopic.php?f=11&t=1400#p5906 We compile our own from source and up to and including 2023.3.0 plaindata2sdds works as expected. Starting in 2023.4.0 and including 2024.1.0 we see that some simple command like the follow...
- 06 Jan 2025, 16:49
- Forum: Installation
- Topic: Undefined Symbol: rpn
- Replies: 6
- Views: 52337
Re: Undefined Symbol: rpn
Thanks. This did the trick and it seems to work for me in 2023.4.0 and 2024.1.0. I appreciate the help.
- 03 Jan 2025, 08:36
- Forum: Installation
- Topic: Undefined Symbol: rpn
- Replies: 6
- Views: 52337
Re: Undefined Symbol: rpn
I have perhaps a similar issue. I've been building elegant from source for years now and starting with version 2023.4.0 I notice that my build is fine, but when I "import sdds" in python3.x I'm getting undefined rpn symbols coming from sddsdata.so. This is the case for 2023.4.0 and 2024.1.0 and seem...