On Sun, 2016-03-20 at 23:36 -0700, carl hansen wrote: > "./configure > --with-lib-path=/home/data1/protected/gnu/lib,/home/data1/protected/gnu/include" > looks wrong, you have a comma separating the "lib" part from "include" part. > First, you can't use comma here, second, the include is include in a > different variable name > (I don't have it in front of me... so I don't try to guess the correct > variable name...)
It's weird to me that Nils included the --with-include-path and --with-lib-path options. Normally, you would use the LDFLAGS and CPPFLAGS environment variables: LDFLAGS="-L/home/data1/protected/gnu/lib" CPPFLAGS="-I/home/data1/protected/gnu/include" ./configure (these are definitely supported by this configure script) However, if you want to try with those other options, you should use both of them (you currently provide the headers directory to the --with-lib-path option: ./configure --with-lib-path=/home/data1/protected/gnu/lib --with-include-path=/home/data1/protected/gnu/include But I think you should actually supplement those with your system paths ./configure --with-lib-path=/home/data1/protected/gnu/lib,/usr/lib --with-include-path=/home/data1/protected/gnu/include,/usr/include -brandon
