search

lballabio / QuantLib-SWIG

QuantLib wrappers to other languages
Other
339 stars 282 forks source link

configure cannot find quantlib-config #7

Closed frgomes closed 8 years ago

frgomes commented 8 years ago

./configure apparently does not honour --prefix and/or --exec-prefix properly since quantlib-config should be found from the location project QuanLib installed it.

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for x86_64-linux-gnu-strip... x86_64-linux-gnu-strip
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking system... Linux
checking for style of include used by make... GNU
checking for x86_64-linux-gnu-gcc... x86_64-linux-gnu-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether x86_64-linux-gnu-gcc accepts -g... yes
checking for x86_64-linux-gnu-gcc option to accept ISO C89... none needed
checking whether x86_64-linux-gnu-gcc understands -c and -o together... yes
checking dependency style of x86_64-linux-gnu-gcc... none
checking for x86_64-linux-gnu-g++... x86_64-linux-gnu-g++
checking whether we are using the GNU C++ compiler... yes
checking whether x86_64-linux-gnu-g++ accepts -g... yes
checking dependency style of x86_64-linux-gnu-g++... none
checking whether x86_64-linux-gnu-g++ accepts warning flags... yes
checking for QuantLib... ./configure: line 4033: quantlib-config: command not found

... despite I definitely have it installed under the location I told QuantLib should install it.

lballabio commented 8 years ago

I don't think that's the purpose of the --prefix argument (and that's not how it's used by the standard autoconf macros). It tells ./configure where to install the program that you're currently compiling, not where to find its dependencies. Those can be specified by setting the PATH environment variable, as in, say, 

PATH=/some/path/bin:$PATH ./configure --prefix=/some/path

Then again, there's also the fact that ./configure doesn't currently honor --prefix as the installation target for some languages. From a quick look, I think it does for Java but not for Python or Ruby. That should be fixed.