Update several i386-mingw32 ports

[blb@…]

Attached are patches to update several cross/i386-mingw32 ports:

• i386-mingw32-w32api to version 3.13, switch pre-extract phase to use extract.mkdir, and indicate it violates the mtree

• i386-mingw32-runtime to version 3.15.2, switch pre-extract phase to use extract.mkdir, and indicate it violates the mtree

• i386-mingw32-binutils to version 2.19.1 (note that files/patch-configure.diff can be removed)

• i386-mingw32-gcc to version 3.4.5-20060117-2

[blb@…]

i386-mingw32-binutils Portfile diff

[blb@…]

i386-mingw32-gcc Portfile diff

[blb@…]

i386-mingw32-runtime Portfile diff

[blb@…]

i386-mingw32-w32api Portfile diff

[landonf@…]

Nice -- please feel free to commit the changes.

[blb@…]

i386-mingw32-w32api in r47659, i386-mingw32-runtime in r47660, i386-mingw32-binutils in r47661, and i386-mingw32-gcc in r47662.

FYI, for i386-mingw32-gcc, the download for g++ uses gcc-g%2B%2B since the plus signs appear not to work with sourceforge...

[ryandesign@…]

Replying to blb@…:

FYI, for i386-mingw32-gcc, the download for g++ uses gcc-g%2B%2B since the plus signs appear not to work with sourceforge...

I don't like this because now the file on our distfiles mirror has those %2B's in its name:

 http://distfiles.macports.org/i386-mingw32-gcc/

And to download the file the link is now:

 http://distfiles.macports.org/i386-mingw32-gcc/gcc-g%252B%252B-3.4.5-20060117-2-src.tar.gz

I note that "port distfiles" says the correct link is:

 http://distfiles.macports.org/i386-mingw32-gcc/gcc-g%2B%2B-3.4.5-20060117-2-src.tar.gz

And that of course does not exist. So we appear to have a bug in MacPorts base that does not properly percent-encode distfile names before appending them to the master_sites URL.

[blb@…]

Replying to ryandesign@…:

I note that "port distfiles" says the correct link is:  http://distfiles.macports.org/i386-mingw32-gcc/gcc-g%2B%2B-3.4.5-20060117-2-src.tar.gz And that of course does not exist. So we appear to have a bug in MacPorts base that does not properly percent-encode distfile names before appending them to the master_sites URL.

Hmm, it seems we're in encoding hell...g++ works for other ports (see gcc43 for example), but if you try to grab the g++ from sourceforge even with curl, it isn't there (and probably the cause of ticket #18628). At least in this case, port should be able to successfully get it from sourceforge until we find the cause; new ticket?

[ryandesign@…]

Replying to blb@…:

new ticket?

Yes: #18736.

[anonymous]

Milestone Port Updates deleted