Re: [CMake] libtool: link: only absolute run-paths are allowed

2014-03-23 Thread Josh Stratton
If I leave off the --prefix for configure, I get the /usr/local/include permission error again. Making install in api /bin/mkdir -p '/usr/local/include' /usr/bin/install -c -m 644 /home/stratton/Public/ppml/external/fftw-3.3.3/api/fftw3.h /home/stratton/Public/ppml/external/fftw-3.3.3/api/fftw3.

Re: [CMake] libtool: link: only absolute run-paths are allowed

2014-03-23 Thread Josh Stratton
When I try specifying the MAKE_INSTALL_PREFIX that way, I get the libtool error again. ... Making all in libbench2 Making all in . libtool: link: only absolute run-paths are allowed make[5]: *** [libfftw3.la] Error 1 make[4]: *** [all-recursive] Error 1 make[3]: *** [all] Error 2 make[2]: *** [fft

Re: [CMake] libtool: link: only absolute run-paths are allowed

2014-03-23 Thread Josh Stratton
Looking at the docs it used a colon with the path afterward. What's the PATH variable for then? On 3/23/14, Michael Jackson wrote: > CMAKE_INSTALL_PREFIX needs an argument which is where you want FFTW > installed. The Default value for CMAKE_INSTALL_PREFIX on Unix type machines > is /usr/local. S

Re: [CMake] libtool: link: only absolute run-paths are allowed

2014-03-23 Thread Michael Jackson
CMAKE_INSTALL_PREFIX needs an argument which is where you want FFTW installed. The Default value for CMAKE_INSTALL_PREFIX on Unix type machines is /usr/local. So your CMake code needs to have something like ExternalProject_Add( fftw SOURCE_DIR /home/stratton/Public/ppml/external/fftw-3.3.3

[CMake] libtool: link: only absolute run-paths are allowed

2014-03-23 Thread Josh Stratton
I've using cmake to build an autoconf portion of the project using ExternalProject_Add. I tried using the autoconf prefix, but was having issues with the libtool and absolute paths. I found DCMAKE_INSTALL_PREFIX in the docs, which seems to avoid the libtool problem, but I'm getting errors saying