On 31 Oct 2008, at 15:16, Gary Dumer wrote: > > > The break down occurs BEFORE the make. It happens during ./ > configure in the shell.
Hmm, odd - I had assumed you were triggering configure (e.g. due to file times or etc) from within the make, as the last message shown in your output is "mingw32-make: *** [makeinclude] Error 1" indicating that mingw32-make has just exited. It's also odd that it complains that it can't create config.status... Is you Msys/mingw install otherwise OK? I mean, you can build other code OK with it and everything? It's odd that fltk would fail like this, if the setup is otherwise good. I am at a loss what else to suggest... >> > MSYS is the last item in my PATH statement, so I don't where it > could be coming from if that's the case. You mean first, surely? You want to be sure that Msys finds it's particular version of any installed utils before it finds any other tools you may have installed on your system. Like if you ever had cygwin, and the build finds some cygwin tools and some mingw tools, well the resulting mix can be "unpleasant"... that sort of thing. > So to summarize: > > 1. Each time I try a new build I download a new fltk tree, even > trying different versions. > > 2. I use Windows XP. > > 3. I have a clean Mingw build with the latest stable version. > > 4. I use the msys shell and follow the suggested procedure outlined > the the article at: http://www.fltk.org/articles.php?L598 > > That's about it , I think. I'm sorry Gary, but I am stumped here - if your Msys/mingw setup is working fine otherwise, then I'm at a complete loss as to why the fltk build doesn't work... I've used this configuration on a lot of machines, from NT4, Win2K, WinXP and Vista, and apart from a little Vista oddness early on, it's always worked just fine. -- Ian _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
