id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
837	Build issue --- using env. variables to find CFITSIO, FFTW	robert.desonia@…	Paul Price	"Our group has been tasked with evaluating pslib for use with LSST. 
(We're not the only ones associated with LSST who are using it or 
trying to use it, but we have been assigned that task).
	
In any case, some build issues have come up that I'd like to report 
as bugs. I can't get into the bugzilla site, so I hope you will 
accept them via email.

1) ./configure needs to be told where cfitsio and fftw are, even 
though environmental variables already point there.

I am installing pslib and its dependencies in a special area 
$LSSTLOCAL. The relevant environment variables are:
setenv LSSTLOCAL ""/array-2/tmp/lsst/local""
setenv PATH $LSSTLOCAL""/bin:""$PATH
setenv LD_LIBRARY_PATH $LSSTLOCAL""/lib:""$LD_LIBRARY_PATH
setenv LDFLAGS ""-L$LSSTLOCAL/lib""
setenv CPPFLAGS ""-I$LSSTLOCAL/include""

I can install cfitsio, fftw, gsl and libxml2 with the usual simple
./configure --prefix=$LSSTLOCAL
make
install
(I also use --enable-float for fftw, to make pslib happy).

But this fails miserably for pslib, even with all those environment 
variables set. Instead I have to explicitly tell it where cfitsio and 
fftw are (it can find gsl and libxml2, presumably using their config 
binaries).

So I end up needing the following to even build the code:
./configure --prefix=$LSSTLOCAL --with-cfitsio=$LSSTLOCAL 
--with-fftw3=$LSSTLOCAL"	defect	closed	high		build	0.12.0	minor	worksforme