From: Alan W. I. <ir...@be...> - 2010-06-06 09:01:50
|
On 2010-06-06 15:55+1000 Sisyphus wrote: > [...] There's some messages in the output about various libraries not being found, > and other things. I'll have to go back and have a closer look at them. > Runnning 'mingw32-make' and 'mingw32-make install' worked fine. Hi Rob: It is good to hear you are now up and running with MinGW on Windows. > > I then tried a re-build, adding the '-DBUILD_TEST=ON' option. > > The c and c++ examples built ok (and the ones I've tried work fine), but > there's a linking problem with the f77 examples that kills the show: > > [snip] > [ 69%] Built target f77_examples > Linking Fortran executable x01f.exe > \home\rob\mingw_vista\i686-pc-mingw32\lib/libmingw32.a(main.o):main.c:(.text+0x1 > 04): undefined reference to `WinMain@16' > collect2: ld returned 1 exit status > mingw32-make[2]: *** [examples/f77/x01f.exe] Error 1 > mingw32-make[1]: *** [examples/f77/CMakeFiles/x01f.dir/all] Error 2 > mingw32-make: *** [all] Error 2 > >> If you don't want to use MinGW make, then there are other CMake generators >> available for your platform corresponding to lots of different build tools. >> Run "cmake --help" to get a full list. >> >> "MSYS Makefiles" is one of those Windows generators I am beginning to gain >> experience with under Wine (a windows workalike available under Linux and >> Mac OS X). That requires a large fraction of MSYS to be downloaded and >> installed including make and bash. But if I recall previous discussion >> correctly, the "MinGW Makefiles" generator you tried to use (which I plan >> to >> try out under Wine fairly shortly) involves just make from MinGW (_not_ >> MSYS) without bash or other MSYS requirements. That simplicity is quite a >> selling point for it which I presume is why that generator has been >> recommended on our Wiki. However, I like the wider availability of more >> tools with the MSYS environment which is why I tried "MSYS Makefiles" (with >> the additional package installs from MSYS that implies) before "MinGW >> Makefiles". > > I'm not greatly fussed as to which I use - and I'll probably experiment with > both. I'll also have to make sure that I can build dynamic libs ok, that the > MinGW ports of gcc-4.x.x also work (I was using gcc-3.4.5), and I'll be > interested to see how things go when I try using a 64-bit build of MinGW. So, > maybe expect some more mail from me on this list in the near future :-) My recent experience with "MSYS MakeFiles" under Wine was with a prerelease version of MinGW-4.5.0. (I am about to try the final version of that release shortly.) For that version of MinGW, the gfortran compiler worked well for our f77 bindings and examples using the "make test_noninteractive" target to do the test. However, there was an internal compiler problem generated by attempting to build our Fortran 95 "f95" bindings. From my further tests using an extremely simplified example for the final version of MinGW-4.5.0, I could make the internal gfortran compiler error go away if I renamed pairs of our routines whose names appeared to be colliding with each other. Thus, my current guess is that problem has to do with a function name hash collision under Wine rather than a general problem that will show up on MicroSoft Windows as well. I don't have access to MicroSoft Windows myself, but when you start using MinGW-4.5.0 on that platform, I will be most interested to hear about your results in comparison with my Wine results. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); PLplot scientific plotting software package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ |