Cygwin has always had trouble with Win9x systems. The problems boil down to trying to simulate a proper OS on a 16-bit single-tasking toy (the whole Win9x family runs on top of DOS, and is painfully limited in its task management). I find Win98SE to be fine for games, but I use W2K for work (and NT4 before that - and I have never had serious problems with "incompatibilities" despite using a horrible mixture of ancient DOS programs as well as every flavour of windows programs, and even some OS/2 programs!).
My advice to people having trouble with running things like msp-gcc on Win98 is to fix the source of the problem - drop Win98. Get a real OS. If you can get away with it, go for Linux (or one of its friends) - if, like me and like many others, you need windows-specific programs programs in your daily work, then use W2K. There are *very* few good reasons for insisting on Win98, especially if you are willing to spend the time reformating your harddisk. Win98 is fine for trying things out, but if you want to do work, and not waste time fighting your system, then the NT line is the only choice for Windows systems. Failing that, make sure you are up-to-date on cygwin. New releases of the key dlls come out regularly, and frequently have comments refering to fixes or workarounds for problems and limitations of Win9x. You could well find that it is simply a matter of downloading the latest cygwin1.dll and using that instead. Failing that, aim for mingw builds. Cygwin attempts to provide (nearly) full posix services to windows programs, which is a lot more than gcc actually needs. Mingw aims lower, aiming to provide key compatibility without simulating missing services, and at a faster speed. It is also perfectly sufficient for compiling gcc, although not for gdb and Insight. David > Steve Underwood <ste...@coppice.org> wrote: > > > Well the problem has reached the right forum, but I still haven't seen > > test1.c. > > Maybe it's this one: > http://www.mikrocontroller.net/sourcecode/msp430/test1.c > > Many people are having problems with the cygwin-built gcc... it > doesn't seem to be very stable, I remember seeing segfaults in "cc1.exe" > very often when I was using cygwin. > > -- > AVR-Tutorial, Forum, über 300 Links: http://www.mikrocontroller.net > > > ------------------------------------------------------- > This SF.net email is sponsored by: Does your code think in ink? > You could win a Tablet PC. Get a free Tablet PC hat just for playing. > What are you waiting for? > http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en > _______________________________________________ > Mspgcc-users mailing list > Mspgcc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mspgcc-users > >
