Ubuntu troubles with cm builds

[paulunderwood]

Originally Posted by EdH

No Joy! ... and, even added /usr/local/lib to my PATH. No progress was made.

Did you export LD_LIBRARY_PATH? See this.

[EdH]

Originally Posted by paulunderwood

Did you export LD_LIBRARY_PATH? See this.

No. This is not familiar to me, but I may have fixed it. I rebooted the machine and all seems 100% happy, including Primo certs, I guess that was needed for the installs to finalize?

Thanks for all your help.


* Actually exporting to LD_LIBRARY_PATH is familiar in that I used it for GPU stuff, but otherwise I'm not familiar with it and it never has anything in it.

[xilman]

Originally Posted by paulunderwood

Did you export LD_LIBRARY_PATH? See this.

Further, it might not be in /usr/local/lib

find / -name libmpfrcx.so -ls | more

should dig it out for you (though it may be hidden in a bunch of clutter from inaccessible directories).

On my machine it gives:

pcl@thoth:~$ find / -name libmpfrcx.so -ls | more
109188130 0 lrwxrwxrwx 1 root root 18 May 8 2022 /usr/local/lib/libmpfrcx.so -> libmpfrcx.so.1.2.3
pcl@thoth:~$

[EdH]

Originally Posted by paulunderwood

Did you export LD_LIBRARY_PATH? See this.

I guess I'm even more confused now. Both the correct way and the incorrect way look the same to me at this page. Or, is that what they are trying to show - that the correct way is incorrect?

find didn't find it anywhere on the newly installed working machine, only 2k+ "permission denied" lines as far as I could tell.

Setting the LD_LIBRARY_PATH did the trick with one of the other non-working machines. I "think" I'm all good to go now.

Thanks for all the help everyone.

[paulunderwood]

Originally Posted by EdH

I guess I'm even more confused now. Both the correct way and the incorrect way look the same to me at this page. Or, is that what they are trying to show - that the correct way is incorrect?

find didn't find it anywhere on the newly installed working machine, only 2k+ "permission denied" lines as far as I could tell.

Setting the LD_LIBRARY_PATH did the trick with one of the other non-working machines. I "think" I'm all good to go now.

Thanks for all the help everyone.

No problem with the helping out.

I must admit I did not set my ROCm library path with LD_LIBRARY_PATH, but merely copied the ".so" to /usr/lib64

[EdH]

For completeness, this procedure proved to work from scratch on an Ubuntu 20.04 machine:

- Obtain cm-0.4.1dev (cm-0.4.1dev-41c4bce.tar.gz) from multiprecision.org
- - This had to be found in the News section of the Introduction, labeled "tarball."

- Obtain mpfrcx (mpfrcx-0.6.3.tar.gz) from multiprecision.org

- untar both packages

- sudo apt install mpc libmpc-dev libmpfr-dev libpari-dev

- move into mpfrcx directory
- - ./configure
- - make
- - make check
- - sudo make install

- whereis libmpfrcx.so.1 This showed it in /usr/local/lib, which is used in the next step.
- export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib/

- move into cm directory
- - ./configure
- - make --enable-mpi
- - make check
- - sudo make install

I then tested both ecpp and ecpp-mpi and uploaded the .primo certificates, without any change, to factordb.com.

After that, I rebooted the machine, tried again and all went well.

[bur]

Just for the record, I had similar troubles with messages about a missing shared object and I could solve it by running sudo ldconfig. Not sure if it's applicable in your case and you solved it anyway, but could still be worthwhile for the future. :)

[EdH]

Thanks for posting. It may help someday, as you suggest.