On Tuesday 01 December 2009 14:51:00 Earnie Boyd wrote:
> Quoting Allin Cottrell <cottrell@...>:
> > I've just tried using the cross scripts to build a Linux-hosted
> > cross compiler, but they're not working -- neither the
> > x86-mingw32-build.sh-0.0-20061107-1 package nor the scripts from
> > CVS. I get 404s from the attempted downloads.
All of them? Or, just binutils-2.20-1-src.tar.gz?
> Bugs related to the SF service and its mirrors isn't something we
> can fix. I suggest a different mirror or just try again the
That would be a fair comment, if we could be sure it is genuinely a
SF issue. If it is just the binutils tarball which fails, then it's
because, (yet again), the source tarball we are providing has been
improperly named; (it is a *generic* source tarball, so it should
*not* be qualified as mingw32 specific; this same issue arose when
we released 2.19, and we agreed on the form shown above).
FWIW, I've just used xscripts CVS HEAD, (which should be no different
from the released package noted above), with configuration updated to
reflect Chris' most recent releases, to update my installation; I had
to manually download binutils-2.20-1-mingw32-src.tar.gz to get past
the improperly named download, and then rename it locally in my local
$PACKAGE_DIR, but the mingwrt and w32api tarballs were successfully
downloaded automatically by the script [*].
[*] When I first saw the original post, I suspected the new
hierarchical organisation of SF's FRS may have invalidated the URI
templates recorded in the script; sure enough, the first wget
attempt for each file failed, but it triggered a redirect and retry,
which subsequently succeeded.