Basically, it needs to be a fully explicit path [absolute
] to ensure there is no relative
path confusion at execution time for dependencies and such—and for Unix security default behavior perhaps.
One must type ./configure
rather than simply configure
to indicate to
the shell that the script is in the current directory. This is
because, as a security precaution, Unix configurations don't search
the current directory for executables. So, to execute programs in that
directory, one must explicitly specify their location.[1]
./configure --libs="-lmpfr -lgmp"
./configure --prefix=/home/user/local
The second line tells make
to install the final version in /home/user/local
Source
A workaround may be to use $(pwd)/xxx
with --prefix
parameter if you cd
or pushd
to the directory you need it to be in relative
wise it will make it absolute
for you dynamically that way expanding it that way using $(pwd)
with the parameter instead.
./configure --prefix=$(pwd)/xxx
Supporting Resources