Hi,
The packaging module in CVS contains the build files for the Windows
installer I produced. It contains a .spec file for an RPM for binutils.
I'm trying to get around to making .spec files for the other parts of
mspgcc. Your script seems like a sensible addition to that area. One
thing, though. The binutils-2.11 stuff is out of date. You should be
using a recent snapshot of binutils from sources.redhat.com. These have
the MSP430 stuff integrated now, and there are bug fixes in there which
are missing from the binutils-2.11 in the mspgcc CVS. The CVS stuff is
no longer updated. We should probably add something to CVS to mark it as
obsolete.
Someone really needs the time to revise the build information on the web
site.
Regards,
Steve
J.C.Wren wrote:
You are correct. And the error doesn't (shouldn't?) really show up
unless
you have an old build laying around that needs the rm'ing, which is why I
missed that. It's welcome to be posted. If so, I'd like to add a 'written
by' with my email address. The copyright part I don't care about.
--John
-----Original Message-----
From: Rick Jenkins [mailto:r...@hartmantech.com]
Sent: Saturday, March 29, 2003 17:39
To: J.C.Wren; mspgcc-users@lists.sourceforge.net
Subject: Re: [Mspgcc-users] Installing the msp430 gcc compiler
Thanks. This works really well, and even points out where I
was going wrong
(as I suspected, wrong source). One working script is worth
any amount of
instructions.
There is a small bug in the script at line 81, which reads:
\rm-rf gcc-3.2.2
missing a space, should be
\rm -rf gcc-3.2.2
I don't know if this is in the original, or a transmission glitch.
This should, with the author's permission, be put up on the
site; it will save
newbies a lot of time.
Thanks again for a great script,
rick
On March 29, 2003 21:56, you wrote:
This is a script I wrote for a friend of mine...
