David Billinghurst <[email protected]> writes: > That works. Thanks. > > Happy to try and answer any mingw questions, but I am not an expert. > In fact, I have been spectacularly unsuccessful in hacking gcl on > windows - > all I have managed to do is keep gcl-2.6.8pre - and now 2.6.8 - > running with gcc-3.3.1 on Windows XP. >
Greetings! I'm certainly no expert, but from my experience with mingw on a real windows machine, there definitely appears to be instabilities in the toolchain. Utilities fail with 'permission denied', mysterious segfaults building gmp are not reproducible, etc. It almost appears as if the entire mingw toolchain suffered from what gcl did until we moved all its memory up above a certain address range. First, I'd like to know if binaries built under some lowest common denominator windows will run on all others. Windows people don't appear to build software frequently, as just one of these issues would grind Linux development to a complete halt. Is it then fruitful to forget about chasing down the buildtime idiosyncrasies in all windows versions and focus for now on one build platform which will run on all others? Take care, -- Camm Maguire [email protected] ========================================================================== "The earth is but one country, and mankind its citizens." -- Baha'u'llah _______________________________________________ Gcl-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gcl-devel
