System call from fortran . . .

Dow:

Were you responding to my reply/post that started with "Some progress."?

I ask because - though your post shows up ahead of that post of mine, it seems quite appropriate to that one.

In any case, I will reply to this post of yours in a "reply" after my reference post.

Tim

Dow:

In response to your question: "What errors did you get when trying to make ngsolve this time?"

I include, "in line", the two posts I made to a discussion on SourceForge, on this very topic (started by another Tim who had the same issue with BLAS and LAPACK not being found during installation.) Those 2 posts are still valid, as far as I can tell. That is, the (two) installations on the two vms ended the same way in each case.

Let me know if you need something different.

Regards,
Tim

Posts on SourceForge
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Post 1, replying to Matthias Hochsteger:

I saw this back and forth a little earlier today. I think I have a relevant observation.
I tried installing netgen/ngsolve on two different ubuntu 17.04 machines today - both are vm's; one fusion and one vbox. Both are on the same MacBook Pro. They both have essentially the same paths (.bashrc) if that matters. I followed the instructions on ngsolve.org in my attempts to install netgen and ngsolve "from source".
In the case of my "main machine", -DUSE_LAPACK=ON in CMakeCache.txt, and neither LAPACK, nor BLAS were found. It did make it through builing/installing netgen, which is my immediate interest.
I just confirmed that -DUSE_LAPACK=ON in CMakeCache.txt on my "side-machine" as well. BUT LAPACK and BLAS were FOUND, and netgen was built/installed. Problems arose during compiling cpp codes. Those problems did not arise on the other machine, but perhaps that is just because the install on my 'side-machine" made it further in cmake/make. (I would need to check, and I don't think that is central to this discussion.)
So, perhaps it is not in the -DUSE_LAPACK=ON setting. Note that the text in CMakeCache.txt files, above the NETGEN_CMAKE_ARGS sections, involve a lot of "info" about both LAPACK and BLAS. I plan to compare the two CMakeCache.txt files.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Post 2, adding more info:

I compared CMakeCache.txt between the two "installations" discussed in my earlier reply.
The two files are very different, and it brought forward at least two things:
I don't really know how cmake works (and hope to never have to really know).
When I got messages that informed me that LAPACK was not found (upon executing cmake), I was told to specify a lib location - where LAPACK could be found. Perhaps CMakeCache.txt is the file to edit?

Hi Tim,

Sorry -- I forgot you said you posted to the SourceForge site. It sounds to me like you may be missing some required libraries on your virtual machines. Did you run this line from the "Build on Linux" page?

sudo apt-get update && sudo apt-get -y install python3 libpython3-dev libxmu-dev tk-dev tcl-dev cmake git g++ libglu1-mesa-dev liblapacke-dev

It sounds to me like you may be missing liblapacke-dev and libblas-dev

To see what libraries you have installed, you can run dpkg --get-selections

Best,
Dow

Dow:

I did run the 'apt-get update && apt-get -y install ...' command in the installation recipe. I actually have done it before each time I have installed.

I located several locations for both liblapack and libblas, when trying to determine the issue wrt "cmake" not finding them. So, I know they are present, but I didn't realize there may be a connection to dpkg.

So, I followed your counsel and ran:
tscale@tscale-mbp-ubuntu:~$ dpkg --get-selections | grep liblapack
liblapack-dev install
liblapack3 install
liblapacke install
liblapacke-dev install
tscale@tscale-mbp-ubuntu:~$ dpkg --get-selections | grep libblas
libblas-common install
libblas-dev install
libblas3 install
libblasr:amd64 install

Does this help?

BTW: It does not reflect the extensive list I get in response to:

sudo find / -name liblapack*

but that might be expected.

Regards,
Tim

Hi Tim,

Thanks for the info -- I was hoping it was something simple. I'll try setting up an Ubuntu 17.04 VM and see if I can reproduce the issue with NGSolve install.

Best,
Dow

Roger that.