Paul Burke wrote:
Message: 7
Date: Mon, 28 Apr 2003 16:42:16 -0400
From: Douglas Kennedy <doug...@comcast.net>
Subject: Re: [Mspgcc-users] compiling in win98
You have the exact same (segmentation error) problem as I have. Sadly, I have
been unable over the last few months to get anyone to accept that msp430
doesn't work with either WIN98 or WINME. Hope you have better luck and that you
aren't shouted down.
I've been using it happily for some time now, but I've not managed to
get the 030306 build to install properly (it keeps whinging about some
cygwin DLL). My binaries are dated 040203. I've never got JTAG running
with W98, so I stick to serial download. I've always preferred working
with spare lines, LEDs and printfs anyway.
The 040203 build uses mingw for binutils and gcc, and cygwin for gdb.
The 030306 use uses cygwin for everything. In both cases the cygwin dll
is needed for gdb. If the 030306 installer works as expected it should
automatically add the mspgcc binary path to your environment PATH
variable, if you use NT, 2000 or XP. On Win98 and Me the installer
should prompt you that you need to add something to your autoexec.bat
file for the mspgcc path. cygwin1.dll should automatically be installed
for any version of Windows if it cannot be found already installed on
your machine. Did you get prompted?
What happens when you try to use the JTAG debugging? I have never built
gdbproxy with cygwin. The windows builds all use mingw. I actually did
most of the Windows development for gdbproxy on a WinMe machine. It
never gave me any trouble there. The windows builds of GDB are always
built with cygwin. You will find various patches around to make GDB work
with mingw, but none of them actually work. The mspgcc GDB never gave me
any trouble on that particular WinMe machine.
I suspect the problem is the lack of a development platform (and will)
among the active developers, and that we poor benighted ones who don't
use Linux will have to get our act together and contribute.
Actually there is plenty of will, and a WinXP machine with this
developer. I hate Window with the strength of someone that has suffered
too much wasted time trying to fight its unnecessary problems. I have to
live with it, though, and I try not to let that get me too pissed off :-)
The cygwin installer has been tried on two Win98SE and WinMe machine I
have access to. The WinMe and one of the Win98SE work fine. The other
Win98SE machine gives such weird results with both the cygwin installer
and the mingw ones that I'm sure there is something screwed up on that
particular machine.
I am amazed how many people care about a Win98 build. I thought most
people doing any development work would be using Win2000 or XP by now,
if they Windows. Win98 is such an unreliable piece of old tat, nothing
is ever very stable on it. If mspgcc crashes, isn't taht par for the
course :-)
Incidentally, allow me to whinge about the W32 distribution: 9Mb is a
big download for those of us who don't have boadband (UK you see, it's
only available in big ciies).
Whinge away. You have made meaningful comments, instead of just
complaining. That earns you the right to a little whinging :-)
That said, most updates causes a variety of changes. The older Windows
installers break things down into a binutils installer, a gcc installer
and a gdb installer. These were always updated as a set, so you needed
to get all three for most updates. That makes the download about the
same size as the single big download. People who want a simple life like
a single installer. They complained about not getting everything in one
simple install. Hence, I made a single all inclusive installer.
You can't please all people all the time, I guess.
Regards,
Steve
