CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > Software User Forums > OpenFOAM > OpenFOAM Installation

Version 15 on Mac OS X

Register Blogs Community New Posts Updated Threads Search

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
Old   March 2, 2009, 15:49
Default Thanks, really appriciated ! I
  #81
Senior Member
 
Pierre-Olivier Dallaire
Join Date: Mar 2009
Location: Montreal, Quebec, Canada
Posts: 192
Rep Power: 17
podallaire is on a distinguished road
Thanks, really appriciated ! I will give it a try

PO
podallaire is offline   Reply With Quote

Old   March 2, 2009, 19:14
Default Bernhard, the patch worked,
  #82
Senior Member
 
Pierre-Olivier Dallaire
Join Date: Mar 2009
Location: Montreal, Quebec, Canada
Posts: 192
Rep Power: 17
podallaire is on a distinguished road
Bernhard,

the patch worked, thanks ! I just want to confirm 2 things :

1) In metis, when building GKlib, I havd this error :

trunk/dlmalloc.c:84: error: conflicting types for 'sbrk'
/usr/include/unistd.h:559: error: previous declaration of 'sbrk' was here
make: *** [Make/darwinIntelDPOpt/dlmalloc.o] Error 1

I commented the declaration of sbrk in dlmalloc.c:84 since it's defined in unistd.h/ does it sound ok ?

2) The error in libhoard comes from :

lnInclude/cpuinfo.h:216: error: cast from '_opaque_pthread_t*' to 'int' loses precision - any suggestion ?

Best regards

PO
podallaire is offline   Reply With Quote

Old   March 3, 2009, 04:41
Default Hi PO! 1. Yes 2. Redefine
  #83
Assistant Moderator
 
Bernhard Gschaider
Join Date: Mar 2009
Posts: 4,225
Rep Power: 51
gschaider will become famous soon enoughgschaider will become famous soon enough
Hi PO!

1. Yes
2. Redefine the lvalue variable and the cast to long

Bernhard
__________________
Note: I don't use "Friend"-feature on this forum out of principle. Ah. And by the way: I'm not on Facebook either. So don't be offended if I don't accept your invitation/friend request
gschaider is offline   Reply With Quote

Old   April 6, 2009, 21:24
Default Salvaging two posts from the old forum
  #84
Super Moderator
 
Takuya OSHIMA
Join Date: Mar 2009
Location: Niigata City, Japan
Posts: 518
Blog Entries: 1
Rep Power: 20
7islands is on a distinguished road
Hi,
As suggested by the forum admin, I am salvaging two posts that were not transferred from the old forum to this new forum thread, both of which I think are important. Note that these posts are not mine but the credits and authorships goes to the respective authors.

Takuya

Between #8 and #9 on this new forum thread:
Quote:
By Pierre-Olivier Dallaire on Saturday, July 19, 2008 - 06:40 pm: Edit Post
Good evening,

I'm sending the detailled procedure that I used to compile OpenFOAM-1.5 on an Intel Mac running under Leopard using Bernhard's patches. Hope this can help:

0) Install some packages :
- The latext XCodeTools ou your machine (download from Apple website) - current version is xcode31_2199 which includes GCC4.2
- Pre-compiled Doxygen binary
- In ~/.profile, add export PATH=$PATH:/Applications/Doxygen.app/Contents/Resources

1) Copy Bernhard's patches in OpenFoam-1.5 and ThirdParty directories

2) Apply those patches in each directory:
patch -p0 <OpenFOAM-1_5-Mac-v1_patch
patch -p0 <ThirdParty1_5-Mac-v1.patch

************************************************** **************
*** Only if you want to use gcc-4.2 instead of gcc-4.0***
Since gcc_select is not anymore available in 10.5, modify some files in wmake/darwinPpc/
- in c, replace gcc with gcc-4.2
- in c++, replace g++ with g++-4.2
- in general, replace cpp with cpp-4.2
************************************************** **************

3) Copy rules (if needed from powerpc to intel architecture):
cp -r OpenFOAM-1.5/wmake/rules/darwinPpc OpenFOAM-1.5/wmake/rules/darwinIntel

4) Modify OpenFOAM-1.5/etc/settings.sh to use current openmpi implementation from Mac OS X (lines 144-146)
mpi_version=openmpi-1.2.3
export MPI_HOME=/usr
export MPI_ARCH_PATH=$MPI_HOME

5) Modify OpenFOAM-1.5/etc/bashrc line 164
MACOSX_DEPLOYMENT_TARGET="10.5"

6) Modify Allwmake in ThirdParty, comment lines 18 to 134 since OpenMPI 1.2.3 is already built-in Leopard

7) Modify line 69 of OpenFOAM-1.5/src/OpenFOAM/primitives/uint/uintIO.C and replace with (as suggested by Bernhard):
i = (unsigned int)(t.labelToken());

8) To build OpenFOAM-1.5:
source etc/bashrc and from OpenFOAM-1.5 :
./Allwmake

9) Build Doxygen doc -> from doc directory :
./Allwwmake

Everything built without problem. I made some quick tests and so far so good. I tried to compile with gcc-4.0 but cht-solver did not make it ...

I did not compile PV3FoamReader since I prefer to download the ParaView3 cvs version and to apply the patch made by Takuya :

http://www.cfd-online.com/OpenFOAM_D...tml?1216503048

Good evening,

Pierre-Olivier

ps : Bernhard, is funkySetfields ready for OF-1.5 ?
Between #80 and #81:
Quote:
By Bernhard Gschaider on Monday, March 02, 2009 - 01:45 pm: Edit Post
I noticed (the Messageboard seems to hate my patches). The patch comes below (hope the messageboard doesn'T mess it up to much)

I remember that I did something about hoard, but I can't remember what.Try

./Allwmake 2>&1 | tee compile.log

and have a look at the start of the log-file (you can stop the compilation as soon as the errors you described above appear)

Index: src/OSspecific/Unix/printStack.C
================================================== =================
--- src/OSspecific/Unix/printStack.C (Revision 932)
+++ src/OSspecific/Unix/printStack.C (Arbeitskopie)
@@ -238,7 +238,7 @@
unsigned valid=0;
bool ok=true;

- for(int level=0;level<maxAddrs;level++) {
+ for(unsigned int level=0;level<maxAddrs;level++) {
if(ok) {
bt[level]=getStackAddress(level);

@@ -265,6 +265,6 @@
int result=dladdr(bt[i],&info);

char tmp[1000];
- sprintf(tmp,"%s(%s+%p) [%p]",info.dli_fname,info.dli_sname,(void *)((unsigned int)bt[i]-(unsigned int)info.dli_saddr),bt[i]);
+ sprintf(tmp,"%s(%s+%p) [%p]",info.dli_fname,info.dli_sname,(void *)((unsigned long)bt[i]-(unsigned long)info.dli_saddr),bt[i]);
strings[i]=(char *)malloc(strlen(tmp)+1);
strcpy(strings[i],tmp);

Index: etc/bashrc
================================================== =================
--- etc/bashrc (Revision 932)
+++ etc/bashrc (Arbeitskopie)
@@ -145,10 +145,6 @@
WM_ARCH=linuxIA64
export WM_COMPILER=I64
;;
- Darwin)
- WM_ARCH=darwin
- export WM_COMPILER=
- ;;
*)
echo Unknown processor type `uname -m` for Linux
;;
@@ -156,22 +152,35 @@
;;

Darwin)
+ export WM_COMPILER=
+ export WM_MPLIB=OPENMPI
+
case `uname -p` in
powerpc)
export WM_ARCH=darwinPpc
;;
i386)
- export WM_ARCH=darwinIntel
+ export WM_ARCH=darwinIntel
+ case $WM_ARCH_OPTION in
+ 32)
+ ;;
+ 64)
+ export WM_COMPILER="64"
+ export WM_CFLAGS='-m64 -fPIC'
+ export WM_CXXFLAGS='-m64 -fPIC'
+ export WM_LDFLAGS='-m64'
+ ;;
+ *)
+ echo Unknown WM_ARCH_OPTION $WM_ARCH_OPTION, should be 32 or 64
+ ;;
+ esac
;;
*)
- echo "This seems to be an Intel-Mac please tell me the output of 'uname -p'. Bernhard."
- export WM_ARCH=darwinIntel
+ echo "This seems to be neither an Intel-Mac nor a PowerPC please tell me the output of 'uname -p'. Bernhard."
+ export WM_ARCH=darwinNone
;;
esac

- export WM_COMPILER=
- export WM_MPLIB=OPENMPI
-
MACOSX_DEPLOYMENT_TARGET="10.4"
;;
*) # an unsupported operating system
7islands is offline   Reply With Quote

Old   April 7, 2009, 06:56
Default
  #85
New Member
 
Peter Johnston
Join Date: Mar 2009
Location: Brisbane, Queensland, Australia
Posts: 25
Rep Power: 17
prjohnston is on a distinguished road
Hello,

I am trying to compile OpenFOAM under Mac OS 10.5 on an intel MacBook Pro. I have followed the instructions like those given, applied the four patches and OpenFOAM compiles and seems to run OK. All the files were placed in directories darwinIntelDPOpt. Also I downloaded cmake 2.6 and Qt 4.5 and was able to build paraview using the buildParaView3.3-cvs. This created files under $HOME/OpenFOAM/Thirdparty/ParaView3.3-cvs/platforms/darwinIntel. In the bin subdirectory of this, the build script created paraview.app. Everything seemed to build OK. My problem is that when I run paraFoam I get the following error message:

/Users/peter/OpenFOAM/OpenFOAM-1.5/bin/paraFoam: line 100: paraview: command not found

I can't find which script file to edit which would fix this problem. Surely, paraFoam must look for Thirdparty/ParaView3.3-cvs/platforms/darwinIntel/bin/paraview.app/Contents/MacOS/paraview. I also realise that this problem had been mentioned before, but I couldn't find a resolution.

Any insights would be appreciated.

Thank you,

Peter Johnston.
prjohnston is offline   Reply With Quote

Old   April 29, 2009, 07:40
Question
  #86
Super Moderator
 
bigphil's Avatar
 
Philip Cardiff
Join Date: Mar 2009
Location: Dublin, Ireland
Posts: 1,089
Rep Power: 34
bigphil will become famous soon enoughbigphil will become famous soon enough
Quote:
Originally Posted by prjohnston View Post

/Users/peter/OpenFOAM/OpenFOAM-1.5/bin/paraFoam: line 100: paraview: command not found
I have got OpenFOAM 1.5 working as well but I also get the same error when I try run paraFoam.


Philip C
bigphil is offline   Reply With Quote

Old   April 29, 2009, 18:50
Default
  #87
New Member
 
Peter Johnston
Join Date: Mar 2009
Location: Brisbane, Queensland, Australia
Posts: 25
Rep Power: 17
prjohnston is on a distinguished road
Dear Philip,

I did find a work around to this for the Mac. When paraview is built it is placed below a directory structure paraview.app (like most Mac applications) in the directory OpenFOAM/ThirdParty/ParaView3.3-cvs/platforms/darwinIntel/bin. The script that drives paraFoam is a unix type shell script which expects the executable file paraview to exist in the above directory. However, on the Mac the executable lives in the directory paraview.app/Contents/MacOS. To overcome this I simply created a softlink:

ln -s paraview.app/Contents/MacOS/paraview paraview

in OpenFOAM/ThirdParty/ParaView3.3-cvs/platforms/darwinIntel/bin. It all seemed to work after that.

I hope this helps. Please ask again if this is unclear.

Good luck,

Peter.
prjohnston is offline   Reply With Quote

Old   April 30, 2009, 05:50
Default
  #88
Super Moderator
 
bigphil's Avatar
 
Philip Cardiff
Join Date: Mar 2009
Location: Dublin, Ireland
Posts: 1,089
Rep Power: 34
bigphil will become famous soon enoughbigphil will become famous soon enough
Hi Peter,

Thanks for your help.

As it turns out, I hadn't compiled Paraview corectly.

Just to sum up the steps, I need to take to compile Paraview:

I downloaded and installed cmake 2.6 (for mac),

Then I downloaded and installed Qt SDK (for mac),

Then I did the following:
• cd $FOAM_INST_DIR/ThirdParty
• rm -rf ParaView3.3-cvs/platforms
• buildParaView3.3-cvs

But Then it seems to get stuck - see below. It stays like this for 20 mins, and then I cancel it. The activity monitor says 'cmake' is doing quite a bit.

• Building ParaView3.3-cvs
• MPI support : OFF
• Python support : OFF
• MESA support : OFF
• Source : //Volumes/OpenFOAM/ThirdParty/ParaView3.3-cvs
• Target : //Volumes/OpenFOAM/ThirdParty/ParaView3.3-cvs/platforms/darwinIntel


Where am I going wrong?

Philip.
bigphil is offline   Reply With Quote

Old   April 30, 2009, 06:17
Default
  #89
Super Moderator
 
bigphil's Avatar
 
Philip Cardiff
Join Date: Mar 2009
Location: Dublin, Ireland
Posts: 1,089
Rep Power: 34
bigphil will become famous soon enoughbigphil will become famous soon enough
I also tried to follow the steps at:
http://paraview.org/Wiki/ParaView:Build_And_Install

But when I get to using 'ccmake', 'ccmake' displays 'cache empty' with no files to configure.

bigphil is offline   Reply With Quote

Old   May 1, 2009, 00:37
Default
  #90
New Member
 
Peter Johnston
Join Date: Mar 2009
Location: Brisbane, Queensland, Australia
Posts: 25
Rep Power: 17
prjohnston is on a distinguished road
I'm not sure what your problem is. I just rebuilt my paraview this morning. It does take a long time, ~45 minutes. Are you some how running you build script in silent mode? (I'm not sure how this could be the case.) Does anyone else have any ideas?

When using ccmake, I realise that it comes up with 'cache empty', but what happens when you type c for configure? There should be a lot of text run through a coloured line at the bottom of the window. At various stages it gives a percentage of how far through the configuration it is.

Which version of Qt do you have?

I can't think of anything else at the moment, but I would be interested to know how you get on.

BTW, does anyone know how to build paraview-3.4 or paraview-3.5 for use with OpenFOAM? That is, paraFoam would use one of these versions of paraview instead of paraview3.3-cvs.

Thanks,

Peter.
prjohnston is offline   Reply With Quote

Old   May 1, 2009, 06:55
Default
  #91
Super Moderator
 
bigphil's Avatar
 
Philip Cardiff
Join Date: Mar 2009
Location: Dublin, Ireland
Posts: 1,089
Rep Power: 34
bigphil will become famous soon enoughbigphil will become famous soon enough
Quote:
Originally Posted by prjohnston View Post
When using ccmake, I realise that it comes up with 'cache empty', but what happens when you type c for configure? There should be a lot of text run through a coloured line at the bottom of the window. At various stages it gives a percentage of how far through the configuration it is.
Peter,

I am using cmake 2.6-patch 1 and QMake version 2.01a Using Qt version 4.5.1.

When I open ccmake, empty cache comes up, then I press 'c' to configure. At the bottom of the screen it says "Configuring, please wait..." but nothing runs across the bottom of the screen.

Maybe there's something wrong with cmake, which version of cmake did you use?

Thanks for your assistance,
Philip
bigphil is offline   Reply With Quote

Old   May 1, 2009, 18:33
Default
  #92
New Member
 
Peter Johnston
Join Date: Mar 2009
Location: Brisbane, Queensland, Australia
Posts: 25
Rep Power: 17
prjohnston is on a distinguished road
Dear Philip,

You sure are having problems. I used ccmake version 2.6-patch 3 and qmake version 2.01a, but I only had Qt version 4.5.0.

I have discovered one problem and that is that paraview assumes that you have Qt version 4.3. If you don't have version 4.3 then the compilation will stop, but usually with an error message. However, since I couldn't find Qt version 4.3 (I could only find the most recent version on the Qt website) I made a change on line 92 of the file CMakeLists.txt file in OpenFOAM/ThirdParty/ParaView3.3-cvs. I had to change the regexp "^4\\.3\\.[0-9]+" to "^4\\.5\\.[0-9]+". It now won't complain if you have version 4.5 of Qt instead of version 4.3.

I'm not sure even this will solve your problem.

A few random thoughts: Are you using a bash shell (things seem to work better than under a [t]csh shell)? Have you employed the patches provided by Bernhard? Have you tried to compile a more recent version of paraview from the paraview site?

I'm not sure if I have been much help, but keep trying.

Peter.
prjohnston is offline   Reply With Quote

Old   May 4, 2009, 08:21
Default
  #93
Super Moderator
 
bigphil's Avatar
 
Philip Cardiff
Join Date: Mar 2009
Location: Dublin, Ireland
Posts: 1,089
Rep Power: 34
bigphil will become famous soon enoughbigphil will become famous soon enough
Peter,

Paraview compiled!

I reinstalled cmake, and then ccmake ran fine.
Paraview opens fine now.
Thanks for your help.

Now the final thing, is getting the 'PV3FoamReader' to compile.


When I execute 'Allwclean' then './Allwmake' in the 'postprocessing/graphics/PV3FoamReader/' directory, I get:


./Allwmake
+ '[' -d //Volumes/OpenFOAM/ThirdParty/ParaView3.3-cvs//platforms/darwinIntel -a -r //Volumes/OpenFOAM/ThirdParty/ParaView3.3-cvs//platforms/darwinIntel ']'
+ case "$ParaView_VERSION" in
+ wmake libso vtkPV3Foam
wmakeLnInclude: linking include files to //Volumes/OpenFOAM/OpenFOAM-1.5-dev/applications/utilities/postProcessing/graphics/PV3FoamReader/vtkPV3Foam/lnInclude
Making dependency list for source file vtkPV3Foam.C
Making dependency list for source file vtkPV3FoamAddVolumeMesh.C
could not open file FieldField.H for source file vtkPV3Foam.C
could not open file lduInterfaceFieldPtrsList.H for source file vtkPV3Foam.C
could not open file GeometricFieldI.H for source file vtkPV3Foam.C
could not open file GeometricField.C for source file vtkPV3Foam.C


Even though, the files which could not be open (such as FieldField.H) are in 'OpenFOAM-1.5-dev/src/OpenFOAM/lnInclude'.

Why can it not open these files? Is it looking in the wrong place? Is it permissions?
Where does 'wmake' look for the dependencies? Or where does one set where it looks for dependencies?

Any ideas are really appreciated,
Philip
bigphil is offline   Reply With Quote

Old   May 17, 2009, 22:13
Default
  #94
New Member
 
Peter Johnston
Join Date: Mar 2009
Location: Brisbane, Queensland, Australia
Posts: 25
Rep Power: 17
prjohnston is on a distinguished road
Dear Phil,

Sorry to have not replied for so long. I seem to have been swamped recently. Have you solved your problem?

My only thought is that you are using v1.5-dev, whereas I was using the
not-so-up-to-date v1.5. I do know that other people are experiencing various problems with the dev version.

Sorry I can't be of more help.

Regards,

Peter.
prjohnston is offline   Reply With Quote

Old   May 18, 2009, 06:54
Default
  #95
Super Moderator
 
bigphil's Avatar
 
Philip Cardiff
Join Date: Mar 2009
Location: Dublin, Ireland
Posts: 1,089
Rep Power: 34
bigphil will become famous soon enoughbigphil will become famous soon enough
Peter,

I haven't resolved the issue yet, but it is fine for the moment as I just use 'foamToVTK' to convert the files and then view them with paraview.

Thanks you for your help,

I haven't spent much time on it recently, but I will let you know if I figure it out.


Best Regards,
Philip
bigphil is offline   Reply With Quote

Old   June 15, 2009, 05:05
Default
  #96
New Member
 
Robert C
Join Date: Jun 2009
Location: London, UK
Posts: 16
Rep Power: 16
ottbot is on a distinguished road
Hello, thanks a lot for your work with the patches and documentation.

It's been mostly painless so far, but I can't get ParaView to find PV3FoamReader..

It built without error, but there's the following warning during compilation:

Code:
CMake Warning at /Volumes/OpenFOAM/ThirdParty/ParaView3.3-cvs/CMake/ParaViewPlugins.cmake:583 (ADD_LIBRARY):
  Cannot generate a safe linker search path for target PV3FoamReader because
  files in some directories may conflict with libraries in implicit
  directories:

    link library [libz.dylib] in /usr/lib may be hidden by files in:
      /Volumes/OpenFOAM/OpenFOAM-1.5/lib/darwinIntelDPOpt

  Some of these libraries may not be found correctly.
Call Stack (most recent call first):
  CMakeLists.txt:43 (ADD_PARAVIEW_PLUGIN)
I'm wondering if this indicates why paraview can't find the plugin, or should I be copying it somewhere or doing something else?

When pavaview opens the cavity demo, it asks me which reader to use.. I'm assuming if the PV3FoamReader was working correctly, it would automatically choose it.. Is it in the list in a non obvious name? The "OpenFOAM files" option crashed (as described earlier in this thread)


Thanks again!

------------------------------
update:
I ran the following commands again:

blockMesh
icoFoam

After this, paraview is finding the reader..

Last edited by ottbot; June 15, 2009 at 13:09. Reason: fix/update
ottbot is offline   Reply With Quote

Old   September 1, 2009, 04:15
Default
  #97
New Member
 
Bjørn
Join Date: Sep 2009
Posts: 3
Rep Power: 16
Bynn is on a distinguished road
Hey all, I´m new to this forum and to OpenFOAM..

I´m having a bit of a problem using the step by step guide found on http://www.ifdmavt.ethz.ch/education...foam/of-macosx <Installation guide>

http://www.ifdmavt.ethz.ch/education.../index#testing
<Testing guide>

When I come to the last part of the testing guide were I´m re-compiling some of OF with wmake I get the following printout:
http://pastebin.com/m19fd8a7f

It´s a long one, but the problem is logically enough on the bottom.

Hope someone can help me, I´m hoping to use OF in my master thesis

I´m on SnowLeopard, but hoping it won´t fuck it up
Bynn is offline   Reply With Quote

Old   September 1, 2009, 10:14
Default
  #98
Assistant Moderator
 
Bernhard Gschaider
Join Date: Mar 2009
Posts: 4,225
Rep Power: 51
gschaider will become famous soon enoughgschaider will become famous soon enough
Quote:
Originally Posted by Bynn View Post
Hey all, I´m new to this forum and to OpenFOAM..

I´m having a bit of a problem using the step by step guide found on http://www.ifdmavt.ethz.ch/education...foam/of-macosx <Installation guide>

http://www.ifdmavt.ethz.ch/education.../index#testing
<Testing guide>

When I come to the last part of the testing guide were I´m re-compiling some of OF with wmake I get the following printout:
http://pastebin.com/m19fd8a7f

It´s a long one, but the problem is logically enough on the bottom.
No it is not. Just near the top in line 41 it says:

ld: warning: in /Users/bjorn/OpenFOAM/OpenFOAM-1.5/lib/darwinIntelDPOpt/libOpenFOAM.dylib, file is not of required architecture

and, as Elvis once sang, "That's where the heartache begins"

Test with the command
file /Users/bjorn/OpenFOAM/OpenFOAM-1.5/lib/darwinIntelDPOpt/libOpenFOAM.dylib

whether you didn't accidentally install the wrong binaries

Quote:
Originally Posted by Bynn View Post
Hope someone can help me, I´m hoping to use OF in my master thesis

I´m on SnowLeopard, but hoping it won´t fuck it up
The binaries are still from the images you downloaded, right? Maybe a complete recompilation of OF would help. Don't know if this is a SnowLeopard-issue (can't imagine why it should be)

Bernhard
gschaider is offline   Reply With Quote

Old   September 1, 2009, 11:25
Default
  #99
New Member
 
Bjørn
Join Date: Sep 2009
Posts: 3
Rep Power: 16
Bynn is on a distinguished road
Hey Bernard!

I ran the command and got the following output:
Code:
/Users/bjorn/OpenFOAM/OpenFOAM-1.5/lib/darwinIntelDPOpt/libOpenFOAM.dylib: Mach-O dynamically linked shared library i386
That was what I was worried about and forgot to tell you in my last post;
my achitecture is i386 and I couldn´t find a solution to it regarding the setup_foam editing...

I´m on a (brand new ) macbook pro 17" running, as I said, SnowLeopard.

EDIT: Ups, well, just saw that I had read that the arch setting in setup_foam was supposed to be ppc, i386 OR Intel
Then I´m back to squar one..

Last edited by Bynn; September 2, 2009 at 02:01. Reason: "progress"
Bynn is offline   Reply With Quote

Old   September 2, 2009, 07:35
Default
  #100
Assistant Moderator
 
Bernhard Gschaider
Join Date: Mar 2009
Posts: 4,225
Rep Power: 51
gschaider will become famous soon enoughgschaider will become famous soon enough
Quote:
Originally Posted by Bynn View Post
Hey Bernard!

I ran the command and got the following output:
Code:
/Users/bjorn/OpenFOAM/OpenFOAM-1.5/lib/darwinIntelDPOpt/libOpenFOAM.dylib: Mach-O dynamically linked shared library i386
That was what I was worried about and forgot to tell you in my last post;
my achitecture is i386 and I couldn´t find a solution to it regarding the setup_foam editing...

I´m on a (brand new ) macbook pro 17" running, as I said, SnowLeopard.
Well. That's an awkward situation:
- first time installing OF on a Mac
- living on the bleeding edge (doing it on a system that nobody else tried yet)


Quote:
Originally Posted by Bynn View Post
EDIT: Ups, well, just saw that I had read that the arch setting in setup_foam was supposed to be ppc, i386 OR Intel
Then I´m back to squar one..
Can't comment on that as setup_foam seems to be specific to the distro you downloaded

Bernhard
gschaider is offline   Reply With Quote

Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
New version fluent file open in Old version ? MANOJKUMAR FLUENT 2 July 10, 2013 04:43
Difference between Version 6.3 and Version 6.2 erikaj FLUENT 0 October 11, 2007 12:36
LES with version 6.3 Steve FLUENT 0 April 26, 2007 15:00
SEM in the 3.5 version Anis Phoenics 0 May 5, 2006 12:41
BUG IN VERSION 3.5!!!!!!!! AERODYNAMIFUN Phoenics 0 May 17, 2004 19:24


All times are GMT -4. The time now is 06:44.