Hi Bryan, > I noticed that config.h does not end up in $prefix/include. If I move > it in from the gsl build directory, programs compile without error. > (my system's /usr/include lacks a config.h). > > so I do not understand this - is make supposed to move config.h into > $prefix/include?
For any project you come across, config.h should almost never be installed into $prefix/include. That header is only meant to provide build-time information to GSL and is not part of the public interface. Having read a few of your recent emails, it sounds like you are installing GSL, then copying individual C source files from the GSL distribution into your project's directories, then compiling them along side your files. If that's the case, it would explain why you see the GSL sources fail to build because of a missing, say, /usr/include/config.h. Are you doing this? The usual thing is to build and install the shared library and it's public header files (e.g. not config.h), and then to link your application against the install GSL binary (documentation in http://www.gnu.org/software/gsl/manual/html_node/Compiling-and-Linking.html where '$prefix/gsl-config --help' can help with the specific details). - Rhys
