make error

Issue #47 resolved
NAVIN SRIDHAR created an issue

Hi,

While installing tempo2, I get this error: libtool: warning: library '/home/cal/ns/mesa/mesasdk/bin/../lib/gcc/x86_64-pc-linux-gnu/8.3.0/../../../../lib64/libgfortran.la' was moved. libtool: error: cannot find the library '/root/mesasdk/lib/../lib64/libquadmath.la' or unhandled argument '/root/mesasdk/lib/../lib64/libquadmath.la' Makefile:751: recipe for target 'tempo2' failed make[2]: [tempo2] Error 1 make[2]: Leaving directory '/home/cal/ns/radio/tempo2-2019.01.1' Makefile:1063: recipe for target 'all-recursive' failed make[1]: [all-recursive] Error 1 make[1]: Leaving directory '/home/cal/ns/radio/tempo2-2019.01.1' Makefile:600: recipe for target 'all' failed make: *** [all] Error 2

Could you please let me know why would that be?

I ran the following check and this is what I found out: locate libquadmath.la /home/cal/ns/mesa/mesasdk/lib64/libquadmath.la

Thank you,

Comments (2)

  1. Michael Keith

    libquadmath is part of the GCC package, so this looks like some problem with your GCC installation rather than an issue with tempo2.

    I'm not really familiar with this type of error, but the ".la" files are text files that describe the location of a library. Libtool uses this to locate the correct library to link against, and any dependencies. This can break if the library were moved after intallation (even if the relative paths haven't changed). I think that what is happening is that even though it can find the .la file, the actual library (likely a .so file) cannot be found. I suggest you check the .la file in question (it is a text file) and see if the paths in there make sense. Otherwise, my main suggestion is to try to solve this warning, e.g. looking through some of these search results:

    https://www.google.com/search?q=libtool+warning+library+was+moved

  2. NAVIN SRIDHAR reporter

    The issue was MESA's SDK, that had its own set of libraries, which was interfering. Moving it resolved the issue. Also, apologies for posting the issue here.

  3. Log in to comment