I've tried building on another XP machine and got the same results (i.e. config.h is a direct copy of config.h.in). I'm starting to think the problem might be with MinGW and the fact that uname -s returns MINGW32_NT-5.1. I will post on the MinGW support forum for help.
Thanks, Armin >>> On 8/18/2011 at 12:26 AM, "Sisyphus" <sisyph...@optusnet.com.au> wrote: > ============================= > > I don't understand it all that well either, but I believe your understanding > > is basically correct. > > In addition to the gcc-3.4.5 that I used yesterday, I also have the very > same setup that you have - namely the one installed by > mingw-get-inst-20110802.exe. > > When I use that, a correct config.h is still being created for me > > I'm fairly sure that your only problem is that your config.h is not being > generated correctly ... and I have no idea why that happens. > > The only differences in our config.log files is the things you would expect > to see as the result of having been run on different machines, different > pathnames, etc. > I can see nothing that explains the reason that your config.h turns out > botched. > > Comparing our 'uname' info: > > uname -m = i686 > uname -r = 1.0.17(0.48/3/2) > -uname -s = MINGW32_NT-5.1 > +uname -s = MINGW32_NT-6.0 > uname -v = 2011-04-24 23:39 > > we see that everything is exactly the same, except for 'uname -s'. I presume > that's merely a reflection of different operating systems (XP versus Vista). > > We probably need some assistance from someone with a better understanding of > > how this config file is supposed to be generated. > > Cheers, > Rob _______________________________________________ Help-gsl mailing list Help-gsl@gnu.org https://lists.gnu.org/mailman/listinfo/help-gsl
