 |
 |
 |
|
|
|
[Sponsors] | ||||
August 24, 2010, 10:38
|
|
#41 | ||||||
|
New Member
Join Date: May 2010
Posts: 13
Rep Power: 16  |
Hi All,
I did an install today from fresh source (ie unpacked the source again, applied the patches etc, so that I could be sure I was starting from a clean slate). To recap, its a dual processor PPC G5 running OS X 10.5.8 I edited line 89 of OpenFOAM-1.7.0/etc/apps/paraview3/bashrc and changed it to ... Code:
mkdir -p $PV_PLUGIN_PATH I then did ... . /Volumes/OpenFOAM/OpenFOAM-1.7.0/etc/bashrc and checked the value of $WM_PROJECT_DIR. "echo $WM_PROJECT_DIR" returned ... "/Volumes/OpenFOAM/OpenFOAM-1.7.0", so I then ran Allwmake. MAKE.LOG OUTPUT There were a lot of lines in make.log like ... Quote:
The make.log file is over 5 meg, but the final section of it reads ... Quote:
TESTING THE INSTALL I noted that a few posts above it reads ... Quote:
So I did this ... Quote:
Quote:
echo $FOAM_RUN returns ... /Volumes/OpenFOAM/bob-1.7.0/run cd $FOAM_RUN/tutorials/incompressible/icoFoam/cavity ... and the terminal confirmed that I was in the cavity directory ... ie /Volumes/OpenFOAM/bob-1.7.0/run/tutorials/incompressible/icoFoam/cavity ... then I did ... blockMesh ... which returned ... -bash: blockMesh: command not found  WHAT TO DO NEXT ? I notice that a few posts above in mattia's post it reads ... Quote:
Should I rerun Allwmake without deleting files as mentioned above ? Where it says above "The paraview binaries available from paraview.org should work fine (I would not bother trying to compile it). All that is will require is for you to create the .foam file in your case root directory." ... where exactly should the .foam file be placed and what should that file contain ? A sincere thank you once again for everyone's help on this. I am really looking forward to being able to run OpenFOAM on this box ! Last edited by AussieRacer; August 24, 2010 at 10:59. |
|||||||
|
|
|||||||
|
August 24, 2010, 12:11
|
|
#42 | ||
|
Assistant Moderator
Bernhard Gschaider
Join Date: Mar 2009
Posts: 4,225
Rep Power: 51 |
Quote:
cd $FOAM_SRC/OpenFOAM wmake libso and see what happens.. Have a look in $FOAM_LIBBIN whether the library is there. Quote:
Bernhard |
|||
|
|
|
|||
|
August 24, 2010, 12:47
|
|
#43 | ||||
|
New Member
Join Date: May 2010
Posts: 13
Rep Power: 16 |
Quote:
Here is the output from: cd $FOAM_SRC/OpenFOAM wmake libso Quote:
Quote:
Code:
cd $FOAM_SRC/OpenFOAM wmake libso Code:
cd $FOAM_LIBBIN echo $FOAM_LIBBIN /Volumes/OpenFOAM/OpenFOAM-1.7.0/lib/darwinPpcDPOpt ls Quote:
Once again many thanks for your help ! Last edited by AussieRacer; August 24, 2010 at 13:09. |
|||||
|
|
|
|||||
|
August 24, 2010, 17:46
|
|
#44 | ||
|
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,982
Blog Entries: 45
Rep Power: 128  |
Greetings AussieRacer,
As you can see, response times may vary  OK, as for the error you are getting: Quote:
Quote:
Code:
gcc -v Bruno
__________________
|
|||
|
|
|
|||
|
August 26, 2010, 10:14
|
|
#45 | ||||||||
|
New Member
Join Date: May 2010
Posts: 13
Rep Power: 16 |
Quote:
You were right - I had installed gcc 4.5 but had forgotten to select gcc 4.5 instead of the built in xcode version of gcc. I have the latest MacPorts versions of gcc_select and Macports gcc 4.5 installed. I then did this ... Quote:
When I installed gcc 4.5 with MacPorts, there were no errors reported. The terminal output of the install of gcc 4.5 with MacPorts reads ... Quote:
RUNNING WMAKE LIBSO AGAIN WITH GCC 4.5 To recap, the attempted OpenFOAM build outlined earlier was using "gcc version 4.0.1 (Apple Inc. build 5490)" which was obviously the wrong version of gcc to use So in my OpenFOAM volume I have the files from that attempted build with gcc 4.0.1 Today I have done this ... Quote:
Quote:
Code:
cd $FOAM_LIBBIN echo $FOAM_LIBBIN /Volumes/OpenFOAM/OpenFOAM-1.7.0/lib/darwinPpcDPOpt ls Quote:
Should ... cd $FOAM_SRC/OpenFOAM wmake libso ... have created a lib named libOpenFOAM ? DO I NEED TO MODIFY THE PATCH ? Bruno your earlier post reads ... Quote:
If so, which file do I need to change and how should that file read after the changes have been applied ? WHAT TO DO NEXT ? Should I now do a fresh build again from source using gcc 4.5 ? Or does the output of "wmake libso" point to another issue I need to fix first ? Once again many many thanks for everyone's help on this. I'm amazed by the depth of knowledge from you guys on compiling OpenFOAM, and without your help I'd be lost at this point with the install. Last edited by AussieRacer; August 26, 2010 at 10:50. |
|||||||||
|
|
|
|||||||||
|
August 26, 2010, 11:46
|
|
#46 |
|
Assistant Moderator
Bernhard Gschaider
Join Date: Mar 2009
Posts: 4,225
Rep Power: 51 |
Hi!
Sorry, I don'T have time to go into details. Just some remark: - gcc45 has problems with OF-1.7.0 (see BUGs-newsgroup). These problems are fixed in 1.7.x so you might consider getting 1.7.x and working on that - I don't recommend using gcc_select to make gcc45 your default compiler (might break other things). Instead specify gcc-mp-45 as the OpenFOAM-compilers in wmake/rules/<your architecture> - I'm attaching an updated version of the Mac-patch - Please note that you'll probably have to adapt the rules for darwinPPC (darwinIntel64 is the one I'm currently using) Bernhard OpenFOAM-1.7.x-Mac_v2.patch |
|
|
|
|
|
|
August 26, 2010, 12:03
|
|
#47 | |
|
New Member
Join Date: May 2010
Posts: 13
Rep Power: 16 |
Quote:
Just to check, when you say "These problems are fixed in 1.7.x so you might consider getting 1.7.x and working on that", by 1.7.x do you mean the source of version 1.7.1 ? Or is 1.7.x a development version ? Thanks again ! |
||
|
|
|
||
|
August 26, 2010, 12:55
|
|
#48 | |
|
New Member
Join Date: May 2010
Posts: 13
Rep Power: 16 |
Quote:
I've now downloaded and unpacked the source files for OpenFOAM-1.7.1 and ThirdParty-1.7.1 I opened the files in /wmake/rules/darwinPPC/ but I am not sure where I need to make the changes and which of those files I need to change to specify gcc-mp-45 as the OpenFOAM-compiler. In /wmake/rules/darwinPPC/c line 5 reads ... "cc=gcc" Should I change that line to read "cc=gcc-mp-45" ? Do I need to make changes to any of the other files in /wmake/rules/darwinPPC/c and if so what changes do I need to make ? Apologies for the basicness of those questions, but I want to make sure that I have got the changes right to avoid creating any problems by not configuring those files correctly. Also do I patch the ThirdParty-1.7.1 files with the patch named "ThirdParty-1.7-Mac.patch" or is that patch only used with 1.7.0 ? Thanks again. |
||
|
|
|
||
|
August 26, 2010, 18:37
|
|
#49 | |||
|
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,982
Blog Entries: 45
Rep Power: 128 |
Greetings AussieRacer,
Sweet, 1.7.1 is out  Quote:
Quote:
Quote:
So, if you haven't forgotten the steps you took for 1.7.0 (editing bashrc and so on), you should be very close to tasting some OpenFOAM 1.7.1 on a MAC PPC Best regards, Bruno
__________________
|
||||
|
|
|
||||
|
August 27, 2010, 05:55
|
|
#50 | ||
|
Assistant Moderator
Bernhard Gschaider
Join Date: Mar 2009
Posts: 4,225
Rep Power: 51 |
Quote:
Quote:
|
|||
|
|
|
|||
|
August 27, 2010, 09:47
|
|
#51 | ||||||||
|
New Member
Join Date: May 2010
Posts: 13
Rep Power: 16 |
Quote:
Today I attempted a fresh build using Macports gcc 4.5 and OpenFOAM 1.7.1 I used Bernard's OpenFOAM-1.7.x-Mac_v2.patch which he posted above to patch OpenFOAM, patched third party using ThirdParty-1.7-Mac.patch, made the changes to /Volumes/OpenFOAM/OpenFOAM-1.7.1/etc/bashrc etc. PARAVIEW3/BASHRC CHANGE On line 89 of OpenFOAM-1.7.0/etc/apps/paraview3/bashrc when I was previously using 1.7.0 I changed ... mkdir $PV_PLUGIN_PATH to ... mkdir -p $PV_PLUGIN_PATH However OpenFOAM-1.7.1/etc/apps/paraview3/bashrc is different to the same file in 1.7.0, so it looks like that change may not be needed as that section of the 1.7.1 file is different. Lines 82-86 in the unedited source OpenFOAM-1.7.1/etc/apps/paraview3/bashrc read ... Quote:
Does it look like those lines remove the need to make the 1.7.0 "mkdir -p $PV_PLUGIN_PATH" change when running 1.7.1 ? WMAKE RULES CHANGES In /OpenFOAM-1.7.1/wmake/rules/darwinPPC/c line 5 reads ... cc=gcc I changed that line to read: cc=gcc-mp-45 In /OpenFOAM-1.7.1/wmake/rules/darwinPPC/c++ I changed in "CC" the "g++" to "g++-mp-45", so that line now reads ... CC=g++-mp-45 When I ran Allwmake though I got a couple of errors ... The very start of make.log reads ... Quote:
http://www.mail-archive.com/trplayer.../msg00281.html reads ... Quote:
Quote:
The final lines of make.log read ... Quote:
wmake libso returns ... Quote:
echo $FOAM_LIBBIN /Volumes/OpenFOAM/OpenFOAM-1.7.1/lib/darwinPpcDPOpt ls returns ... Quote:
Thanks again. |
|||||||||
|
|
|
|||||||||
|
August 27, 2010, 10:00
|
|
#52 | ||||
|
New Member
Join Date: May 2010
Posts: 13
Rep Power: 16 |
Quote:
In today's attempted install posted above I used your OpenFOAM-1.7.x-Mac_v2.patch to patch OpenFOAM 1.7.1, and patched third party using ThirdParty-1.7-Mac.patch. Is that the correct procedure I should use ? cd /Volumes/OpenFOAM/OpenFOAM-1.7.1 patch -p1 <OpenFOAM-1.7.x-Mac_v2.patch returned ... Quote:
patch -p1 <ThirdParty-1.7-Mac.patch returned ... Quote:
Quote:
When you say "for the first experiments I wouldn't bother trying to recompile paraview", do you mean that instead of using /OpenFOAM-1.7.1/Allwmake that instead I should use /OpenFOAM-1.7.1/Allwmake.noThird ? Can you spot anything in the post above this one that might be causing the problem I am having with installing 1.7.1 ? Thanks again. Last edited by AussieRacer; August 27, 2010 at 10:24. |
|||||
|
|
|
|||||
|
August 27, 2010, 10:21
|
|
#53 | |
|
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,982
Blog Entries: 45
Rep Power: 128 |
Hi AussieRacer,
I assumed "gcc-mp-45" and "g++-mp-45" are the names of the executables for gcc and that you had already tested them. Try running them with "-v" option in a terminal/console and see if anything happens. If it doesn't find those executables, you possibly need to add the path to those binaries in the variable PATH... but like I've said before, I don't have experience with Mac OS X, so I'm only guessing when it comes to Mac specific information So, you might need to add something like this to your ~/.bashrc file: Code:
export PATH=$PATH:/usr/gcc-mp-45/bin/  Quote:
At least for now...Best regards, Bruno
__________________
|
||
|
|
|
||
|
August 27, 2010, 11:17
|
|
#54 | ||||||||
|
New Member
Join Date: May 2010
Posts: 13
Rep Power: 16 |
Quote:
g++-mp-45 -v -bash: g++-mp-45: command not found gcc-mp-45 -v -bash: gcc-mp-45: command not found WHICH G++ TO USE ? In /opt/local/bin there are 2 G++ executables named ... g++-mp-4.5 ppc-apple-darwin9-g++-mp-4.5 g++-mp-4.5 -v returns ... Quote:
returns ... Quote:
WHICH GCC TO USE ? In /opt/local/bin there are 3 GCC executables named ... gcc-mp-4.5 ppc-apple-darwin9-gcc-4.5.1 ppc-apple-darwin9-gcc-mp-4.5 gcc-mp-4.5 -v returns ... Quote:
returns ... Quote:
returns ... Quote:
Quote:
Quote:
That's what I meant where I said "do you mean that instead of using /OpenFOAM-1.7.1/Allwmake that instead I should use /OpenFOAM-1.7.1/Allwmake.noThird". ie since I have Paraview 3.8 already running on this box from a Paraview Mac OS X Universal Application Bundle, should I run /OpenFOAM-1.7.1/Allwmake or should I run /OpenFOAM-1.7.1/Allwmake.noThird ? A huge thank you to you guys for your patience with me and my OpenFOAM newbie questions ! I really appreciate your help and though I ask a few questions at the beginning I learn fast and don't ask the same questions again and again That's also why I've put so much detail into my replies as that may help other newcomers to OpenFOAM in the future get up to speed quickly.
Last edited by AussieRacer; August 27, 2010 at 11:36. |
|||||||||
|
|
|
|||||||||
|
August 27, 2010, 11:59
|
|
#55 | |||
|
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,982
Blog Entries: 45
Rep Power: 128 |
Hi AussieRacer,
These seem to me the best choice for now: Code:
ppc-apple-darwin9-gcc-mp-4.5 ppc-apple-darwin9-g++-mp-4.5 Quote:
Code:
export PATH:$PATH:/opt/local/bin Quote:
Quote:
Good luck! Bruno
__________________
|
||||
|
|
|
||||
|
September 11, 2010, 08:17
|
|
#56 | |||||
|
New Member
Jan Löhrmann
Join Date: Sep 2010
Posts: 21
Rep Power: 16 |
Hi All,
I'm having some problems with compiling OF-1.7.1 for my Mac OS X 10.6. and hope somebody might be able to help me! I'm just starting to use terminals and stuff like that so as far as I know I had to do a bit of groundwork before. What I have done so far: 1. Downloaded and installed xcode. 2. Downloaded and installed MacPort 1.9.1. 3. Created a case-sensitive disk image in my user directory. 4. Extracted OF-1.7.1 and ThirdParty-1.7.1. 5. Downloaded the patches OpenFOAM-1.7.x-Mac_v2.patch and ThirdParty-1.7-Mac.patch and patched them using: Quote:
Quote:
6. I've checked the compiler with gcc -v and it listed gcc 4.2.1 as current compiler. So I installed gcc45. When using the command gcc -v it now returns: Quote:
7. With a bit of effort I then sourced the etc/bashrc, which should be ok too. 8. Afterwards I tried ./Allwmake in the OF directory and it showed this, which I abborted shortly afterwards: Quote:
Quote:
1. Is it correct, that the start of the make.log says "Start ThirdParty Allwmake", though I originally intended to compile OF? 2. What might produce the Errors shown in the make.log? 3. Should I have installed any more programs, so that OF is able to run (already installed cmake and flex, which seem to be necessary for Ubuntu according to the "cookbook" ( http://hvirvel.dk/OF/installOF9.10 ), or are such programs not necessary for Mac or maybe already included in xcode or MacPort)!? 4. If worst comes worst, I'd consider trying to run OF for Ubuntu via "Parallels" on my Mac. Does anybody have experience with that? Any help and ideas would be very much appreciated. And as I'm a total newbie, please be patient with my basic questions ! |
||||||
|
|
|
||||||
|
September 13, 2010, 05:59
|
|
#57 | |
|
Assistant Moderator
Bernhard Gschaider
Join Date: Mar 2009
Posts: 4,225
Rep Power: 51 |
Quote:
@3: you'll need cmake for the Paraview-stuff but apart from that everything you need should come with XCode @4: VirtualBox works as well for that. |
||
|
|
|
||
|
September 13, 2010, 11:40
|
|
#58 | |
|
New Member
Jan Löhrmann
Join Date: Sep 2010
Posts: 21
Rep Power: 16 |
Hi Bernhard,
thanks for the help! Quote:
|
||
|
|
|
||
|
September 14, 2010, 06:50
|
|
#59 | |
|
Assistant Moderator
Bernhard Gschaider
Join Date: Mar 2009
Posts: 4,225
Rep Power: 51 |
Quote:
BTW: the files should live in $FOAM_SRC/OpenFOAM/meshes/primitiveShapes/objectHit |
||
|
|
|
||
|
September 14, 2010, 07:29
|
|
#60 |
|
New Member
Jan Löhrmann
Join Date: Sep 2010
Posts: 21
Rep Power: 16 |
Hi Bernhard,
you were right! There is only the file pointHit.H and not PoinHit.H! I'm a bit confused here... My Mac OS system is case-insensitive but I created a case-sensitive image and untarred the files within this image! Is there anything I have to consider for creating such an case-sensitive image in a case-insensitive system/environment or maybe any typical mistakes I could do working with such an image? I guess I'll try to create a new image and start from the beginning again!? Thanks for your help!!! |
|
|
|
|
|
 |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| [blockMesh] Default patches not appearing in paraview | ozzythewise | OpenFOAM Meshing & Mesh Conversion | 9 | September 22, 2017 10:51 |
| [snappyHexMesh] internal faces between patches created with snappyHexMesh | romant | OpenFOAM Meshing & Mesh Conversion | 0 | August 17, 2009 09:40 |
| Courant number, patches, etc | oort | OpenFOAM | 1 | July 24, 2009 19:05 |
| [snappyHexMesh] SnappyHexMesh large number of patches written | prapanj | OpenFOAM Meshing & Mesh Conversion | 0 | July 15, 2009 09:11 |
| radiation patches, viewfactors | beams | Siemens | 1 | March 12, 2009 08:39 |
Traits<Foam::Switch>)’ is ambiguous
ne'
Linear Mode
