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 ...

I applied the changes to bashrc as wyldckat suggested.

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 ...

... similar to what Mattia reported a few posts above.

The make.log file is over 5 meg, but the final section of it reads ...



TESTING THE INSTALL

I noted that a few posts above it reads ...

So I figured I'd try to run the tutorial and see if it works.

So I did this ...

The tutorial docs read ...

So I did this in the terminal ...

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 ...

I am a bit stuck as to what I should do next, so any help anyone can advise would be hugely appreciated.

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 !

The intestesting part is in the beginning .... All the applications complain that they don't find libOpenFOAM which, as the name indicates, no OF-application can live without. To check it should be sufficient to

cd $FOAM_SRC/OpenFOAM
wmake libso

and see what happens..

Have a look in $FOAM_LIBBIN whether the library is there.

If the OF-library was not there before the "wmake libso" and afterwards it is, try the Allwmake-script again

Bernhard

Hi Bernhard,

Here is the output from:

cd $FOAM_SRC/OpenFOAM
wmake libso

Does that shed any light on it ? (the forum rendered the smileys in there) I'm not sure exactly what I should be looking for in that output.

After running ...

... if I do:

... that outputs ...

Should there be a file / directory in /Volumes/OpenFOAM/OpenFOAM-1.7.0/lib/darwinPpcDPOpt named libOpenFOAM ?

Once again many thanks for your help !

Greetings AussieRacer,

As you can see, response times may vary ;)

OK, as for the error you are getting:
I think it's because you are using a gcc of the 4.2.x generation! Are you sure you are using gcc 4.5?
To check what version you are using, run:Best regards,
Bruno

Hi Bruno,

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 ...

Is it normal for gcc -v to give that error when using gcc_select ? Or is there something wrong with my gcc-mp-4.5 install ?

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 ...



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 ...

That returned ...

Does that output above shed any light ? That output is quite different to the earlier output when I was using the wrong version of gcc, so I assume that gcc 4.5 is now being used to execute wmake libso, especially as I used "sudo gcc_select mp-gcc45" before executing wmake libso.

now returns ...

... so again there is no sign in /Volumes/OpenFOAM/OpenFOAM-1.7.0/lib/darwinPpcDPOpt of a file named "libOpenFOAM" or similar.

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 ...

Do I need to make a change to the patch as per your post at http://www.cfd-online.com/Forums/openfoam-bugs/78964-openfoam-1-6-x-1-7-0-1-7-x-not-fully-prepared-work-gcc-4-5-x.html#post271787 ?

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.

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



Attachment 4508

Many thanks for your prompt reply Bernhard. I have downloaded the updated version of the patch and will let you know how I go with it.

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 !

Hi again Bernhard,

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.

Greetings AussieRacer,

Sweet, 1.7.1 is out :D
Cool, this way you (and MAC users in general) won't need to apply that post I made the other day about "-fno-strict-aliasing".


You also need to edit "/wmake/rules/darwinPPC/c++" and change in "CC" the "g++" to "g++-mp-45", if I'm not mistaken.


I can only guess that there weren't any substantial changes between ThirdParty-1.7.0 and ThirdParty-1.7.1, so it should be OK.

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

Best regards,
Bruno

The v2 patch I posted yesterday works on 1.7.x from three days ago. So it should work on 1.7.1, too

BTW: for the first experiments I wouldn't bother trying to recompile paraview. Download a 3.8 (I hope they still provide that fro PPC) and use the native reader (just do "touch foo.foam" in the case directory).

Hi Bruno,

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 ...

... so the line "mkdir $PV_PLUGIN_PATH" is no longer there in 1.7.1

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 ...

ERROR 127 INFO

http://www.mail-archive.com/trplayer.../msg00281.html reads ...

http://www.mail-archive.com/trplayer.../msg00283.html reads ...

RESULTS OF MY ATTEMPTED OPENFOAM BUILD

The final lines of make.log read ...

cd $FOAM_SRC/OpenFOAM
wmake libso

returns ...

cd $FOAM_LIBBIN
echo $FOAM_LIBBIN
/Volumes/OpenFOAM/OpenFOAM-1.7.1/lib/darwinPpcDPOpt
ls

returns ...

Does anyone know what might be causing this ?

Thanks again.

Hi Bernhard,

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 ...

cd /Volumes/OpenFOAM/ThirdParty-1.7.1
patch -p1 <ThirdParty-1.7-Mac.patch

returned ...

PARAVIEW

Yes I have Paraview 3.8 running already on this box from a Paraview Mac OS X Universal Application Bundle.

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.

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:As for the new patches: its only natural that they get more refined over time :)

I believe that he meant that you shouldn't waste time running the makeParaView script that is in the ThirdParty folder ;) At least for now...

Best regards,
Bruno

My mistake - I have done some compiling from source in the past but am a bit rusty. Thanks for your patience ! I assumed they were the correct names of the executables too.

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 ...

ppc-apple-darwin9-g++-mp-4.5 -v

returns ...

Should I specify "g++-mp-4.5" or "ppc-apple-darwin9-g++-mp-4.5" in the /OpenFOAM-1.7.1/wmake/rules/darwinPPC/ files ?


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 ...

ppc-apple-darwin9-gcc-mp-4.5 -v

returns ...

ppc-apple-darwin9-gcc-4.5.1 -v

returns ...

Should I specify "gcc-mp-4.5" or "ppc-apple-darwin9-gcc-mp-4.5" or "ppc-apple-darwin9-gcc-4.5.1"" in the /OpenFOAM-1.7.1/wmake/rules/darwinPPC/ files ?


I'm definitely not complaining about the patches in any way. They are a huge timesaver and I hugely appreciate the time and effort that Bernhard has put into the patches and yourself and Bernhard's time in answering questions.


Will running the Allwmake script at /OpenFOAM-1.7.1/Allwmake attempt to build OpenFOAM and Paraview or will it only build OpenFOAM without attempting to build Paraview ?

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.

Hi AussieRacer,

These seem to me the best choice for now:
They have the complete naming and will avoid future issues with MacPorts updates, such as 4.5.1 that seems incomplete, by what I can see from your post.

Like I said before, you might need to add "/opt/local/bin" to your PATH variable:Once again, I should have been more specific: makeParaView is an independent script and usually isn't called from the Allwmake scripts, because makeParaView was created to re-build ParaView no matter what... so it would be a serious pain if it was called every time you ran Allwmake.

My guess: run Allwmake, since this way you will get all of the libraries available for OpenFOAM :)

Good luck!
Bruno

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:

The patch for ThirdParty went through normal! When patching the OF patch sth like this occured:

I've hit "n" a couple of times and the rest of the patch went through normal. Unfortunately I don't know how to reproduce the exact sequence!?

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:

which I assume to be correct!?

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:

The make.log keeps on going on like this and at some point starts to return that:

Questions:

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

Just @point 2: my guess is that you're not working on a case-sensitive filesystem. The missing file PointHit.H has a brother pointHit.H living in the same directory and then the Highlander-effect ("There can be only one") hits.

@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.

Hi Bernhard,

thanks for the help!

I'm quite sure the image I produced with the disk utility program is case sensitive (Format: Mac OS Extended (case-sensitive and journaled))! I can also create both folders "test" and "Test" within this image. Could I have done anything else wrong here? Do you have an idea what to try next?

Check wheher you have both: pointHit.H and PointHit.H. Is it possible that the directory you're working with "visited" a case-insensitive filesystem (for instance you untarred the sources there and then moved them to the final destination).

BTW: the files should live in $FOAM_SRC/OpenFOAM/meshes/primitiveShapes/objectHit

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!!!

If the image is case-sensitve (and you tested that if I remember it correctly) and you untarred directly onto it all the files should be there. No additional requirements that I know of

Hi,

I just untarred the OF- and Thirdparty-file again on the case-sensitive image and now it seems that the files are complete (e.g. there is now a PointHit.H and a pointHit.H file!). So I patched everything again and copied the files bashrc and settings.sh, which I previously changed from the old directory in the new one and ran ./Allwmake.

At first it looked good and no errors (at least I didnt spot any) were shown until:
Afterwards there came up several warnings of this style:

And later on there were a whole bunch of files which could not been opened:

It keeps on going like this for quite a while!

It ends like this:

I checked if those missing files exist and they do!
Any idea what could have gone wrong?

I tried the foamInstallationTest and the result is this (maybe it helps to find the error!?)

I tried again ./Allwmake and spotted the following warnings, which might be relevant!?

and:

I really don't know where the error might be or what it might cause! Do these quotes help anybody to find the problem?

Thanks very much for your support!

I try really hard to find any instruction on how to install OpenFOAM on mac, but despite my best intentions, I cannot find the right information.

Could anyone kindly post what steps are required to follow in order to have OpenFOAM-1.7 up and running on Mac Snow Leopard machine?

Thank you!

Try this:
http://chrisjbutler.wordpress.com/20...for-os-x-10-6/

Chris Butler

Thanks a lot, clear guide. However as I compile, it keeps going for about 15 minutes then it quits with following error

In file included from /Users/user/OpenFOAM/OpenFOAM-1.7.x/src/OpenFOAM/lnInclude/NamedEnum.H:120:0,
from /Users/user/OpenFOAM/OpenFOAM-1.7.x/src/OpenFOAM/lnInclude/time.h:50,
from /usr/include/wchar.h:113,
from /opt/local/include/gcc45/c++/cwchar:47,
from /opt/local/include/gcc45/c++/bits/postypes.h:42,
from /opt/local/include/gcc45/c++/bits/char_traits.h:42,
from /opt/local/include/gcc45/c++/string:42,
from /Users/user/OpenFOAM/OpenFOAM-1.7.x/src/OpenFOAM/lnInclude/string.H:51,
from /Users/user/OpenFOAM/OpenFOAM-1.7.x/src/OpenFOAM/lnInclude/stringList.H:35,
from /Users/user/OpenFOAM/OpenFOAM-1.7.x/src/OpenFOAM/lnInclude/argList.H:73,
from mixtureAdiabaticFlameT.C:33:
/Users/user/OpenFOAM/OpenFOAM-1.7.x/src/OpenFOAM/lnInclude/NamedEnum.C: In constructor 'Foam::NamedEnum<Enum, nEnum>::NamedEnum()':
/Users/user/OpenFOAM/OpenFOAM-1.7.x/src/OpenFOAM/lnInclude/NamedEnum.C:34:18: error: template argument 3 is invalid
/Users/user/OpenFOAM/OpenFOAM-1.7.x/src/OpenFOAM/lnInclude/NamedEnum.C:34:19: error: expected '{' before '(' token
/Users/user/OpenFOAM/OpenFOAM-1.7.x/src/OpenFOAM/lnInclude/NamedEnum.C: At global scope:
/Users/user/OpenFOAM/OpenFOAM-1.7.x/src/OpenFOAM/lnInclude/NamedEnum.C:34:20: error: expected unqualified-id before numeric constant
/Users/user/OpenFOAM/OpenFOAM-1.7.x/src/OpenFOAM/lnInclude/NamedEnum.C:34:20: error: expected ')' before numeric constant
/Users/user/OpenFOAM/OpenFOAM-1.7.x/src/OpenFOAM/lnInclude/token.H:386:25: warning: inline function 'void Foam::token::operator=(int*)' used but never defined
make[2]: *** [Make/darwinIntel64DPOpt/mixtureAdiabaticFlameT.o] Error 1
make[2]: Target `/Users/user/OpenFOAM/OpenFOAM-1.7.x/applications/bin/darwinIntel64DPOpt/mixtureAdiabaticFlameT' not remade because of errors.
make[1]: *** [mixtureAdiabaticFlameT] Error 2
make[1]: Target `application' not remade because of errors.


Trying to fix it, additionally, in OpenFOAM-1.7-Mac.patch I changed all the required entries to gcc-mp-4.5, but error still persists.

$FOAM_APPBIN is empty.

Any tips?

Thanks,
P

I am not that great (yet) with the errors. I have two suggestions:

Try with another build of OpenFOAM:
To get the latest head from the git repo:
git reset
git pull $OF_GIT_ADDRESS
Then re-apply the patch

OR to get the 1.7.1 build
git reset
git checkout -b master version-1.7.1
Then re apply the patch.

Make sure your OF directory and Third party directory version names match i.e. 1.7.1 or 1.7.x.

Try with another compiler:
Perhaps try gcc4.4 or gcc4.3.

I hope someone else will be more helpful!

Cheers,
Chris Butler

Thanks a lot for a prompt reply!

The thing was, somehow the disk image did mount the right way and actually I used non-case dependent OpenFOAM/ folder which I created earlier. After mounting the partition in the right way compile process moved forward.

However, I still have one question. As the compile process ended it finished with the following output message:

make: Target `application' not remade because of errors.

I'm not sure how to interpret it. Any help in this matter?

Thanks,
P

BTW. $FOAM_BINAPP points to:
/Users/user/OpenFOAM/OpenFOAM-1.7.x/applications/bin/darwinIntel64DPOpt

and the folder lists bunch of different apps, so at least in some part applications folder was created.

You'll have to look up a bit in the logfile (I recommend always compiling with './Allwmake 2>&1 | tee compile.log' as probably your terminal will be to short). Probably the tecplot-converter and the PV3Reader-plugin didn't get compiled (but the rest was)

Hi,

really really sorry to bother you guys but does anyone have an idea what might have been the problem while compiling OF, which I have tried to describe in my post from the 14.09. (7pm)? I'd extremely appreciate any help, as I don't have any clue!!!

PS: In the link which Chris uploaded I've seen the following command:

Is that necessary for OF to work? In that case it might be my problem, as I haven't done that so far! An is the command the same if you use OF-1.7.1?

Again: Thanks for your support!!!

Seems OK to me (foamInstallationTest finds icoFoam). The tecPlot-converter doesn't compile on Mac OS

No. Its just another way to get the sources. Either you do that or you use a tar of the release

Jan,

Follow post from the Chris blog. It is simple and clear description of the whole installation process.

Bernard, thanks for the tip. Right now as much as I had time to test things distribution is up and running.

Best,
K

Greetings to all!
Hi Bernhard, I'm sorry I can't help you guys out more, but since I can't get access to a Mac, my hands are tied :(
Nonetheless, I know someone who probably has already fixed that issue with tecPlot: Richard Smith at Symscape has patches for OpenFOAM 1.7.x, for building it for both Windows (cross-compiling) and Mac (compiling) - http://www.symscape.com/openfoam-1-7...windows-64-mpi

edit: FreeFOAM should also have this issue solved, but it's a bit harder to adapt from it :(

Best regards,
Bruno

PS - FYI: I've studied these patches (at blueCAPE :D) and created modified patches for cross-compiling OpenFOAM in Linux for Windows, but also including most of OpenFOAM's Third Party software, and also improving on top of Symscape's patches :D

Thanks for the hint, Bruno.

Only did a brief attempt to fix the tecplot-stuff but as I don't use TecPlot myself and nobody every complained I didn't spend too much time on it. I'll have a look at the patches

Just going through OpenFOAM tutorials I noticed one of the solvers did not compile.

I tried to compile it separately and at the end all solvers as a whole, all is fine except interFoam (and Tecplot, but I don't need that one). Any tip regarding that?

Thanks!

Greetings Paka,

The inter*Foam solvers seem to be missing an option:Edit the files Make/options in each solver's source code folder and add it to EXE_LIBS.

Best regards,
Bruno

Hi All,
Does anybody knows for running OpenFOAM 1.7 on MacBook it requires OS X snow leopard (10.6) or OS X tiger (10.4) also can be used?
thnx

Bruno,

Strange, it is the original source code, shouldn't it be just fine to compile regardless of platform on which I run it?

I tried to add that option inside the source code, but the problem still persists. Please find present output in attached txt file.

Thank you,
K

PS. Answering Babak's question, OpenFOAM should run on any OS X operating system (including Tiger).

Forgive me. This time I modified each of the Make/options file from each of the solvers. This time the solvers compiled, however, what makes me uncomfortable is the bit with "unused variable" as you can see in previously attached output file, log2.txt.

Thanks for your time and help!
K

Hi Paka,

Don't worry about that, it also happens in the Linux version. Those warnings are related to some variables that are defined in a general header file that is used by several solvers. I believe that some use them, others don't. And since the solvers with the warnings work without any problems, it's probably left in the low priority queue of "FIXME" list :)

Best regards,
Bruno