Hi Bernhard.
Thanks for this page.
Could you please verify: you're not using the latest version of XCode (5.0.1)? I had a report of 1.6-ext-nextRelease not compiling with that (have no time to verify it myself).
Only wondering as you're alsready using Maverik
Thanks Bernhard
Hi Bernhard,
sorry for my late reply, I didn't see your question until Bruno informed me about it.
I've successfully compiled it on Mountain Lion with both Xcode versions: v5.0.0 and v5.0.1 (current release) However, I didn't try to compile the nextRelease yet. And I also didn't compile it on Mavericks, although I intend to do so, soon. After I saw that some macports couldn't be compiled straight away, I downgraded from Mavericks back to Mountain Lion. Means I have no conclusive report on Mavericks yet.
Thanks for your many many contributions to the OpenFOAM community :) I'll let you know in case I manage to compile the nextRelease on Mountain Lion or Mavericks, or the current release on Mavericks.
Cheers, Bernhard
Which compiler did you use? MacPorts or the one from XCode? Because the latter caused some problems (not for me. I use the MacPorts-compilers)
I used the MacPorts compiler: g++ (MacPorts gcc46 4.6.4_3) 4.6.4
Why does the installation of MacPorts require the xcode command line tools? Do you have an idea why I was not able to install rpm via MacPorts on Mavericks? (Since I downgraded back to Mountain Lion, I cannot reproduce error messages right now... you might still have a clue, though :)
I guess MacPorts requires the command line tools because although they deliver binary packages nowadays technically it is a "source only"-distro and even if it would use its own compiler it would need some compiler to bootstrap the compilation of that. Which happens to be the XCode-compiler. Plus there may be other utilities that are MacOS-X specific and for which no OpenSource-alternative exists (the linker?)
About rpm: without the error message it is hard
