[ndev]

Hi All,

Complied foam 3.2 (from github extend mirror) on a cluster recently and all went fine, until I got to swak4foam...then one major issue came up:

- Seems that between 3.1 and 3.2 the "triSurface" source code moved from the root of "src" into "meshTools" where it was combined with another folder named "triSurface"

- This is confusing to swak, which is trying to link directly to the triSurface library...but it is now in meshTools...

- My hack to fix it was to both put a symbolic link in the "src" directory for "triSurface" pointing to the folder in mesh tools, as well as remove the "-ltriSurface" from all the swak libraries' Make/options files. This seems to make swak happy, and the final compile is happening now.

Has anyone else run into this? What's the more permanent fix that keeps swak happy with all the versions of foam-extend?

[milad653279]

ok. I have the same problem.

[wyldckat]

Originally Posted by ndev

Has anyone else run into this? What's the more permanent fix that keeps swak happy with all the versions of foam-extend?

Quick question: Are you using the latest swak4Foam release version? Or which specific version of swak4Foam are you using?

[ndev]

I'm using swak4Foam-0.3.2 which is the version included in the third party rpm build with foam-extend-3.2 on the github mirror. Thanks!

[wyldckat]

Hi ndev,

OK, I've spotted the origin of the problem. What happened is that you possibly do not have Mercurial installed, which resulted in the script "AllMake.stage5" going for the secondary solution that relies on the SVN repository.
Problem is that the current 0.3.2 version on the SVN repository isn't as up-to-date as the Mercurial version, as Bernhard somewhat mentioned on Twitter: https://twitter.com/swakPyFoam/statu...97349514776577

If you are using Ubuntu, you can install Mercurial with the following command:

sudo apt-get install mercurial

Then you can rebuild swak4Foam by running:

foam3rdParty
rm -r ./rpmBuild/BUILD/swak4Foam-0.3.2
./AllMake.stage5 > log.swak4Foam 2>&1

Best regards,
Bruno

[ndev]

Great! I'm on a cluster where I don't have access to software/module installation, but I'll definitely ask the admins to add Mercurial for next time! I guess I just assumed that Mercurial and SVN were two different ways to get at the same code! Thank you for clarifying this!

[jesse_wang]

Originally Posted by wyldckat

Hi ndev,

OK, I've spotted the origin of the problem. What happened is that you possibly do not have Mercurial installed, which resulted in the script "AllMake.stage5" going for the secondary solution that relies on the SVN repository.
Problem is that the current 0.3.2 version on the SVN repository isn't as up-to-date as the Mercurial version, as Bernhard somewhat mentioned on Twitter: https://twitter.com/swakPyFoam/statu...97349514776577

If you are using Ubuntu, you can install Mercurial with the following command:

sudo apt-get install mercurial

Then you can rebuild swak4Foam by running:

foam3rdParty
rm -r ./rpmBuild/BUILD/swak4Foam-0.3.2
./AllMake.stage5 > log.swak4Foam 2>&1

Best regards,
Bruno

Dear Bruno,

I followed your instruction about the re-installation of swak4Foam, but still the problem couldn't be fixed.

"icoIbFoam: error while loading shared libraries: libtriSurface.so: cannot open shared object file: No such file or directory"

This error message happens when I tried to run a solver from foam 3.2 standard database. As well, I tried to compile my solver based on this foam 3.2, errors reveal that ltrisurface.so is missing.

ps. I have compiled the foam 3.2 again, after the installation of mercurial.

Best Regards,

Jesse

[wyldckat]

Greetings Jesse,

Whatever problem that is, it's not related to swak4Foam itself. Please run the following commands:

foam
./Allwmake > log.make 2>&1
gzip < log.make > log.make.gz

Then please attach the file "log.make.gz" to your next post. This will tell us what went wrong with building foam-extend 3.2.

In addition, please tell me what the following commands give you:

gcc --version
g++ --version

And please tell me which Linux Distribution you are using.

Best regards,
Bruno