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

Bgschaid (talk)19:11, 29 October 2013

You do not have permission to edit this page, for the following reasons:

  • The action you have requested is limited to users in the group: Users.
  • You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.
  • Your username or IP address has been blocked. The block was made by DNSBL. The reason given is Your IP address is listed as an open proxy in the DNSBL used by OpenFOAMWiki..
    • Start of block: 09:34, 9 May 2024
    • Expiry of block: 09:34, 9 May 2024
    • Intended blockee: 52.14.224.197
    You can contact DNSBL or another administrator to discuss the block. You cannot use the "email this user" feature unless a valid email address is specified in your account preferences and you have not been blocked from using it. Your current IP address is 52.14.224.197, and the block ID is #. Please include all above details in any queries you make.

You can view and copy the source of this page:

Return to Thread:Talk:Installation/Mac OS/OpenFOAM-1.6-ext/Version of XCode/reply.

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)

Bgschaid (talk)22:32, 12 November 2013

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 :)

BernhardGrieser (talk)20:00, 13 November 2013

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

Bgschaid (talk)13:24, 16 November 2013