From: Ralf W. <Ral...@gm...> - 2011-08-26 12:37:27
|
* Earnie wrote on Fri, Aug 26, 2011 at 01:55:49PM CEST: > Ralf Wildenhues wrote: > > * Armin Armbruster wrote on Mon, Aug 22, 2011 at 05:36:57PM CEST: > >> On a positive note: > >> I installed a XP virtual machine (also SP3) on my computer. I installed > >> the same MinGW/Msys package on the VM and the same gsl-1.15 sources. Lo > >> and behold, the ./configure script ran fine in the virtual machine and > >> produced a proper config.h. and make ran through fine and compiled > >> properly. > >> I can't see any significant difference in the config.log file between the > >> two machines (other than the hostname and some path settings), so it is > >> not clear to me why it works in one case but not the other. > > > > Can you compare the two respective config.status files? > > If you see differences you cannot make sense of, can you send > > the broken one, after gzip'ing it? > > > > Usually things like that happen when sed or awk (used to transform > > config.h.in to config.h) can't match input strings, for line ending > > or other w32-related reasons. > > Also when path names contain spaces it will screw up the build. Actually, as long as configure was called with a relative file name, and only Autoconf and Automake (but not Libtool) were involved, things should work fine even if the absolute file name contains a space. At least it used to work with some recent versions of Autoconf and Automake. So, a bug report for a counterexample would be appreciated. Thanks, Ralf |