From: Mirko B. <mir...@ie...> - 2006-06-13 20:37:25
|
thank you Brian, in fact you guessed it right and I had to make GSL reachable from the default gcc include and lib paths by simlinking (previously it was only under /opt, though appropriately referred by its pkg-config file) I didn't bother in the past to include some extras like amcl, so I never got into such a problem with GSL, but I wonder if the fact that ./configure --help outputs "Some influential environment variables: ... GSL_CFLAGS C compiler flags for GSL, overriding pkg-config GSL_LIBS linker flags for GSL, overriding pkg-config ... " is just a misunderstanding due to autoconf/automake issues, or what else ... after reading it, I believed that GSL conf was going on through pkg-config ... anyway, everything is ok now, thanks cheers Mirko Bordignon - University of Padova, Italy mirko[dot]bordignon[at]ieee[dot]org Il giorno 13/giu/06, alle ore 21:46, Brian Gerkey ha scritto: > > On Jun 13, 2006, at 10:10 AM, Mirko Bordignon wrote: > >> Hi there, >> I was recompiling p/s to have the latest 2.0.2 up and running, and >> for some reasons it refuses to build amcl due to gsl not found; btw, >> gsl is in place and I double checked its pkg-config metadata to >> ensure it's pointing to the correct lib and include dirs ... any >> idea? > > Have a look in config.log, searching for 'gsl'. You should find some > information about why the test failed. > > It looks like amcl is requiring the header <gsl/gsl_version.h> to be > available, rather than for pkg-config to be able to find the GSL (I > believe the GSL started providing a pkg-config file only with version > 1.5, and 1.4 is still in wide use). > > brian. > > > _______________________________________________ > Playerstage-users mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-users |