Hi Bruno.

Wow, thank you very much for your quick and detailed reply. I'm impressed!

Just a quick update, I am using Ubuntu 10.04 LTS. I am trying out your suggestions today and will let you know the results.

Regards,
Thomas

Hi Thomas,
You're welcome! I'm also thankful to you for giving such a detailed report, otherwise I would still be clueless as to why building Scotch was such a tricky business!

Interesting, it's same version I've used for the development of the patches. Therefore the problem has to be another.

I've given it some thought and I think I know why the patches have worked for me and not for you and Billy: I've always been using 2 or more cores for building the whole thing, while you guys use only one core. This means that with me, libscotcherr gets built in parallel and ends before libscotch is built, therefore with me this issue has never happened before! But for you guys, with single core, libscotch had to be built before libscotcherr. This is not much of a problem in Linux (except in Fedora 13), since libraries can have loose links, but with Windows DLLs, there has to be a very clear existence of the necessary libraries!

I'll update the patches ASAP to fix this problem. But hopefully things should now go well for you Thomas, since the instructions I gave you are the ones I'm going to follow to fix the patches :) But nonetheless, please give me some feedback if it has worked or not!

Best regards,
Bruno

Hi again Bruno.

Ok short update. Everything seems to work! Scotch build without problems and openFOAM has just finished building INCLUDING snappyHexMesh.exe. I'm currently compiling the documentation and the tutorials and haven't tested OF yet but will get back to you when I get a chance to test the build.

With regards to the error DOS_Mode.bat gives I have uploaded a screen shot of it, however because of my OS (Win 7), it is Danish.

A rough translation would be:

Procedureentrypoint_ZTVN10_cxxabiv117_class_type_i nfoE was not found in DLL-library libstdc++-6.dll.

I believe the error is because I have a python distribution installed which has a local copy libstdc++-6.dll which is on the Windows PATH. When DOS_Mode.bat sets an additional PATH to the OF version of libstdc++-6.dll you get problems.

I tested my previous compilations of OF at work where they ran without any problems, so I believe the above error is only a problem at my home computer.

Kind regards,
Thomas.

Hi Thomas,

Sweet! Once again, thanks for the feedback :)

As for that error with "libstdc++.dll", the trick is to:

1. Edit the file "setvars.bat";
2. Go near the end of the file and find the line that starts with:
   Code:

   ---

   set PATH=%PATH%;%MPI_ARCH_....

   ---

3. Now move the string "%PATH%;" to the end of the line, and use a semi-colon ";" to separate "%PATH%" from the previous end of that line.
4. Save and close. And voilá, it's fixed :D

This way Windows default PATH gets pushed to the end, and Python will no longer get in the way :) Although there might be an issue if you try to use the python command in that window... or perhaps there won't be, if python has the library it needs in the same folder as the python executable file.


By the way, I haven't checked this in Windows, because I mainly use Windows in English, so if you have any problems using ParaView 3.8.0 to open the ".foam" files, it's likely due to your Windows being in Danish. In Linux I know this is an issue with locales different from English (explained here), so you can try the same trick in Windows:

1. Edit the file "paraFoam.bat";
2. Add this line, before the "start paraview" line:
   Code:

   ---

   set LC_ALL=C

   ---

3. Save and close.

Try running paraFoam now in the "Windows Command Line" and see if ParaView now behaves well :)

Best regards,
Bruno

Hi Bruno.

I have tested the new compilation of OF and everything works, including snappyHexMesh! Your tip about putting %PATH% at the end of the line in setvars.bat also worked perfectly. Thank you very much for all your help.

I haven't found out if there's any problems with parafoam. I simply use paraView and foamToVtk, but thanks for the tip though.

I have a few final comments on the build.

1) When I run any openFOAM command in get the following warning.

// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
--> FOAM Warning :
From function openLibrary(const fileName& libName)
in file MSwindows.C at line 1142
\ LoadLibrary failed. "Error 126: Det angivne modul blev ikke fundet.
"

Is that a problem or just part the porting from linux to Windows?

2) In the section "9.2 Packing up and leaving for Windows" I think I have found a small error. The code :

should be changed to:

3) In the setvars.bat file, what does the line "%HOME%\Ruby187\bin\setrbvars.bat" do? In my version of discretizer it includes it's own ruby distribution, why is there a need to set the path when you start OF?

Again thank you very much for all you help.

Kind regards,
Thomas.

Hi Thomas,
It's probably a bug on my part :( Sorry about. It shouldn't affect operationality, since it's just a warning. But did you do this step while still in Linux:Weird, I thought I changed them all! Thanks for the report! (Edit: I just fixed this one! The others will have to wait a few more hours...)

Ooops, that's a leftover from the blueCFD package; it sets up the Ruby environment so Discretizer can be launched from the command line.

And Thank You as well, because it's good thing you reported about all of these issues! The release we made of blueCFD 1.7-1 had none of these issues, because I fixed them as I found them and always used multi-core, so none of these issues ended up in the final product... but the documentation in the wiki didn't get the same testing treatment :(

Hopefully tomorrow I'll get to fixing these issues.

Best regards,
Bruno

Hi Bruno.

I did run
Both of the files are present in my ".\OpenFOAM-1.7.0\lib\linuxmingw-w32DPOpt" directory. Wierd, but if it is not a problem I won't worry about it and concentrate on doing some CFD :).

Regards,
Thomas.

I have try and get some bugs, this is my build log
I use 7.1 Using custom built MinGW cross-compilers
after use
I did follow 7.3.1
and cd to OpenFOAM project and
Did i miss st??

Hi Mr.Cloud,

That's an old issue, due to the evolution of the "cpp" binary.
Edit the file "$WM_DIR/rules/$WM_ARCH$WM_COMPILER/general" and make the 1st line look like the first one from here: https://github.com/OpenCFD/OpenFOAM-...nuxGcc/general

Namely this one:
Best regards,
Bruno

First thanks for your quickly reply and i edited that file follow your tutorial but it still the same...
Is there sts wrong at file ~/OpenFOAM/ThirdParty-1.7.0/ParMetis-3.1/Make??

Hi Le Phi Long,

OK, I finally managed to get around to test this. Run the following commands:
You should now no longer see any major problems for the ThirdParty folder.

Now you can move onto the OpenFOAM folder:
This way you get a full build log in the file "make.log", so it's easier to keep track of the errors that occur.

Best regards,
Bruno

Oh... THanks you so much Bruno... I have done follow you, and it got no error so far...

Hi Bruno,I was success in buiding OF 1.7.x for win 64, and thanks you so much for that..., Now i'm building version 2.1.0. I has an release from Ect and it's work well but I need build and OF source to make my thermal foam (simpleThermal,...). I followed this tutorial http://www.symscape.com/openfoam-2-1...windows-64-mpi but got alot of error .
I user the mingw-w64, with this version, i was success in build a OF1.7.x version. Looking for your tutorial like version 1.7, so detail and comfortable.

This is the begin...

This is my buildlog so far.
Here is the full log https://docs.google.com/document/d/1...-D3iu1mh0/edit
I terminated it when i got these errors.

Hi Mr.Cloud,

If you still have problems with this, I suggest you start a new thread for the instructions you are following, instead of asking the same question on multiple threads :p
(the duplicate question I'm talking about is this one: http://www.cfd-online.com/Forums/ope...tml#post379260 )

Best regards,
Bruno

Ok... Thanks for your reply Bruno. From now i will post my problems to this thread "OF 2.1.0 under Windows XP or Windows 7", it look suitable with my problem than this. And can you come there, and have a look at my problem?
Thanks you so much. And st, please forgive for my poor English.

Problem when patching ThirdParty-1.7.0
 

Hi,

I am trying to cross compile OpenFoam1.7 in cygwin, I therefore used the wiki instructions on:
and
The installataion of Cygwin went fine (as far as I know).
In one of the first steps of the second link, however, when patching ThirdParty-1.7.0, I get the error_

...and then it asks me for the file to patch.

Anybody any clue? (I don't know anything about linux so I'm following the wiki instructions like a blind robot... ..and hope to end up with win32 executables :o)

Greetings gerritgroot,

I did a quick test in Ubuntu and it's very simple:

1. When it asks that question "File to patch:", you simply press the Enter key.
2. It then asks if it should skip it, for which you answer:
   
   Code:

   ---

   y

   ---

   And press the Enter key.

And you're good to go onward! Don't worry about this particular file not being patched, because that was a glitch the patch that I created back then. Said file will be properly fixed during compilation!

Best regards,
Bruno

PS: I moved your post to this thread, because this is the thread dedicated to questions for the patches posted for that series of instruction pages.

"File to patch?"
 

Muito obrigado Bruno,:)

I never thought it would be that simple. I'm sure more questions will come up as this is all new to me.

Gerrit.

BTW: It took me some time to find my own messages back. Isn't there a button like "my messages" somewhere? (I've seen that on other forums)

Hi,

As was to be expected, I got stuck again. I hope you can help me out.

First of all some downloads didn't work. I solved this by placing the compressed files under the "download" directory:
Then after uncompressing and building the compiler I got the following error
which made me have a look in the log file where I found:

So, to solve this, I typed:
at the CygWin prompt.

And ran the script again
The script seems clever enough to skip the downloading of the files if they are available. Nevertheless, I got the same error again at the very end.

How can I solve this?