That fixed it. I'd like to figure out why it busted it someday. ;)
-----Original Message-----
From: 'Dick Porter' [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 02, 2002 2:16 PM
To: Kenneth Benson
Cc: '[EMAIL PROTECTED]'
Subject: Re: [Mono-list] Latest mono-build-w32 problem
On Thu, May 02, 2002 at 01:50:21PM -0400, Kenneth Benson wrote:
> The first time I ran it, it complained about not being able to rename
> .new.mono-build-w32.sh.
> I figured that it was trying to update it from the CVS but was locked due to
> being in use.
> I copied the .new.* file to mono-build-w32.sh and that's when the problem
> started. Did someone
> update the mono-build files?
I updated the file recently so that it chooses the stable autotools, but the
script wont try and update itself unless you're running the version in
the checked out CVS directory.
Try commenting out the lines that say:
if [ ! -z "${AUTO_STABLE}" -o -e /usr/autotool/stable ]; then
export AUTO_STABLE=${AUTO_STABLE:-/usr/autotool/stable}
export AUTO_DEVEL=${AUTO_STABLE}
fi
This shouldnt break anything, but its the only change for a while.
- Dick
