[gccsdk] GCC 4.1.2 release 1 package won't upgrade from theprevious version

Alan Buckley alan_baa at hotmail.com
Thu Apr 26 00:50:56 PDT 2012

John Tytgat wrote on Wednesday, April 25, 2012:

> > When using RiscPkg or PackMan to update the GCC4 it fails
> > with a dialogue files that conflict with the file:
> >
> > Selecting-the-Target-System/html
> >
> > I've tracked this down to a change in the case of this
> file between the two releases.
> >
> > The old version was:
> >
> > Selecting-The-Target-System/html
> >
> > Note the capital 'T' in 'the'.
> >
> > Would it be possible to restore the old case in the
> > packages and upload a new version?

> Those html pages are automatically generated during kit generation so
> a rename afterwards is quite fiddly and I don't see how we can avoid
> similar instances of this problem in the future.  I would like to
> avoid that.

> Are you actually saying RiscPkg/PackMan isn't able to deal with filename
> case changes between two versions of a package ?

Yes I am saying that.  The shared back-end (libpkg) to both versions uses
an exact match to figure out which files it can overwrite during an upgrade
so sees them as different files, but they won't be on the disc.

> If so, any chance to get
> this fixed in RiscPkg/PackMan itself ?

As it's difficult for you to change, I will email the author of libpkg to
see if he can get it changed.

Do you know if it is safe to assume that RISC OS filenames are not
case sensitive?

In the meantime people will need to uninstall GCC4 and then install it

I was hoping you had the files on a disc somewhere still so you could
just rename that one file and rebuild the one package.

Is this possible for the current release? If not, would it be OK with
you if I rebuilt a new version of the package from your version with
the one files case changed?

I will also pursue what can be done with libpkg to see the same
problem doesn't occur in a future release.


More information about the gcc mailing list