Originally Posted by ajmas

Quote:
Originally Posted by ajmas View Post
Current status update on my efforts:
- https://github.com/ajmas/OpenFOAM-2.3.x master branch includes most of the changes available in this thread
- I have created a build script, attached to this post that should make building much easier. Doing the following:
-- Creating and mounting case-sensitive HFS+ disk image
-- Getting the necessary MacPorts (if you use another tool, please contribute changes)
-- Cloning the git repository (uses mine, since it is already patched)
-- Configuring bashrc
-- initiating the build
-- Ensuring the build is outputted to log
For anyone using MacPorts be sure to check your PATH environment variable. Be sure to put /opt/local/bin at the start, to avoid MacOS X versions of commands taking precedence.

I found this due issues resulting from the using of the version of flex at /usr/bin/flex. The MacOS X default version will fail in certain cases.

I have also now put the script for the build script on GitHub: https://github.com/ajmas/scripts-et-...sx-macports.sh

And with all this it all builds

Originally Posted by Petru (Post 536434)

Hi,
Thank you for your help.
It is finally working!!!!!
After some hours of building, the installation is now complete without any error...now I have just a question:
Is the installation permanent?
I mean, now I think everything is inside the volume, if I remove it, what is going to happen? Will I lose everything (the installation)? How can I make it permanent?
Sorry but I am not very good in this kind of things.
Thank you again,
it was very useful, specially for who is not good enough as me!!!

All the best,
Paolo

Originally Posted by ajmas (Post 530626)

Current status update on my efforts:
- https://github.com/ajmas/OpenFOAM-2.3.x master branch includes most of the changes available in this thread
- I have created a build script, attached to this post that should make building much easier. Doing the following:
-- Creating and mounting case-sensitive HFS+ disk image
-- Getting the necessary MacPorts (if you use another tool, please contribute changes)
-- Cloning the git repository (uses mine, since it is already patched)
-- Configuring bashrc
-- initiating the build
-- Ensuring the build is outputted to log

Please let me know if this helps you and please provide any pull-requests or change suggestions.

Note, I still waiting for my current build to finish, so will see if it is successful.

Originally Posted by maCrobo (Post 536632)

Thanks for the effort. What patches are you using? I'm asking that because it appears that defining paraview as a function avoids some issues with paraFoam. In fact, the user Alexejm did that in his patch and it seems pretty easy and quick a change. I'm advising it because lately on 3 different macs (1 with Mavericks, 2 with Yosemite) I met the same issue: everything installed smoothly, but paraFoam calls gives an error, which seems related to the alias definition used in Bernhard Gschaider's patch (using a function definition solves the problem).

Originally Posted by ajmas (Post 536648)

I used a number of patches from the thread. You can see the source code in GitHub.

I encountered some issue using the paraFoam command too, since paraview.app doesn't support the .openFoam extension. If anyone has this working I'll integrate this into my fork.

Originally Posted by ajmas (Post 537081)

Thanks @maCrobo for the suggestions, I have now applied them.

Using 'paraFoam -builtin' seems to help, though should we be trying to do anything with PV4Readers (request if param is not specified)?

Originally Posted by maCrobo (Post 537243)

As far as your doubt goes, I got the impression that those PV4Readers are used for the Linux distribution of Paraview. In fact, it seems that if you want Paraview on Linux you have to compile it, and those PV4 files are there to modify some features (i.e. some buttons and panels) and have Paraview directly handle OpenFoam file format.

Originally Posted by maCrobo (Post 537243)

Finally, the simple paraFoam command (without any options) doesn't work on MacOS.

Originally Posted by alexeym (Post 537323)

Not exactly. You can install Paraview binary package on Linux and use 'paraFoam -builtin'. Built-in OpenFOAM reader has certain problems (it does not understand uniformFixedValue boundary conditions for example) and certain advantages (it can read decomposed cases). Also you can build Paraview from sources on OS X (http://www.paraview.org/Wiki/ParaView:Build_And_Install) and after you can try to build PV4Readers. As from time to time people can not follow short OpenFOAM's installation guide, Paraview & PV4Readers build will be overkill.

Originally Posted by maCrobo (Post 537577)

Is there a way to get rid of the uniformFixedValue "misunderstanding" ?

Originally Posted by totalart (Post 487069)

I have successfully installed OF 2.3.0 following the instruction in Alexey Matveichev's blog. Everything's okay except snappyHexMesh. Following error occurs with SHM(I'm not running parallel).

dyld: Symbol not found: __SCOTCHbgraphbipartststratab
Referenced from: /Users/totalart/OpenFOAM/OpenFOAM-2.3.0/platforms/darwinIntel64ClangDPOpt/lib/openmpi-system/libptscotchDecomp.so
Expected in: flat namespace
in /Users/totalart/OpenFOAM/OpenFOAM-2.3.0/platforms/darwinIntel64ClangDPOpt/lib/openmpi-system/libptscotchDecomp.so
Trace/BPT trap: 5


In the Allwmake log, there was no error but warnings only. Anyone can advise what the problem is?

Many Thanks,
Young-kook

Originally Posted by alexeym (Post 487368)

Hi,

well, it appeared that previous patch had more problems than I though. So here is a new patch for 2.3.0 - https://bitbucket.org/mrklein/openfo...20140421.patch.

Unfortunately, due to the problems with dynamicCode in previous patch, you need to rebuild everything. The list of bugs in previous patch that was fixed in the new one:
- mess with DYLD_LIBRARY_PATH, now I think it is finally correct
- error in Allwmake for ptscotch decomposition method (this was the reason for the error)
- error in wmake/Makefile (OpenFOAM code expected dynamic library to have extension .dylib while in Makefile it was .so, and that breaks dynamicCode functionality)
- Clang over-optimization of limited schemes that lead to FPE

Originally Posted by KateEisenhower (Post 537851)

Has anybody experienced this problem as well?

Originally Posted by alexeym (Post 537874)

Hi,



I have tried to reproduce the error you posted. OS X 10.10.2, OpenFOAM 2.3.1, patch from github. Unfortunately I was not successful. On my laptop everything runs perfectly well.



Not quite sure they are the same. I think patch on Github contains certain additional corrections.



You can just remove (delete) disk image you have created during installation.

Originally Posted by alexeym (Post 537874)

Hi,



I have tried to reproduce the error you posted. OS X 10.10.2, OpenFOAM 2.3.1, patch from github. Unfortunately I was not successful. On my laptop everything runs perfectly well.



Not quite sure they are the same. I think patch on Github contains certain additional corrections.



You can just remove (delete) disk image you have created during installation.

Originally Posted by KateEisenhower (Post 538098)

I reinstalled OpenFOAM 2.3.1 and had a look at the log.Allwmake file afterwards. I was quite surprised to find many warnings and "could not open file" outputs. Is this normal? It is 11.7 MB big. So unfortunately I can't upload it here.

---

dyld: Symbol not found: __SCOTCHbgraphbipartststratab
  Referenced from: /usr/local/opt/scotch/lib/libptscotch.dylib
  Expected in: flat namespace
 in /usr/local/opt/scotch/lib/libptscotch.dylib
Trace/BPT trap: 5

---

Originally Posted by alexeym (Post 538106)

Hi,



You can use Dropbox to share the file. You can use Github to share the file. You can use Bitbucket to share the file. Surely you will need account on one of these services. The first is user-friendly, the second and the third are developer-friendly.

---

$ sw_vers
$ gcc --version
$ clang --version

---

Originally Posted by alexeym (Post 538437)

@KateEisenhower

I have reproduced your error (finally) and it was really due to change in Homebrew's Scotch build process (i.e. they moved from static library to dynamic library and ptscotch now needs -lscotch during linking). Fortunately the fix is rather simple. You have two possibilities:

1. If you still have OpenFOAM installed, do the following

2. If you removed OpenFOAM. Start from the beginning. Now patch is adapted for the new version of Scotch.

Originally Posted by alexeym (Post 538674)

Hi,

As the path in error is

I would suppose you did not set up environment variables, because this is the line in the script where it sources RunFunctions

as your environment was not set up, $WM_PROJECT_DIR is expanded into empty string.

Originally Posted by alexeym (Post 539258)

Hi,

Maybe here it is written clearer - https://github.com/mrklein/openfoam-...-configuration.

If you were able to build OpenFOAM, then once you have set up environment variables. In general it is done with 'source $HOME/OpenFOAM/OpenFOAM-2.3.1/etc/bashrc' command. But before issuing this command you have to mount disk image with case sensitive file system you have created.

Originally Posted by alexeym (Post 539405)

Hi,

1. Really, I have omitted this in guide. You should be in $HOME folder (/Users/kateeisenhower).

2. In general on Unices ~ refers to home folder, so your ~/.profile is /Users/kateeisenhower/.profile.

You can check if installation succeeded by executing Allrun in Terminal instead of Finder. I.e. in the terminal, where you have mounted disk image and then executed 'source $HOME/OpenFOAM/OpenFOAM-2.3.1/etc/bashrc', you write (text starting from # is a commentary)