Opened 13 years ago
Closed 8 years ago
#31578 closed update (wontfix)
Update i386-mingw32-gcc to latest version
Reported by: | mojca (Mojca Miklavec) | Owned by: | landonf (Landon Fuller) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | cooljeanius (Eric Gallager) | |
Port: | i386-mingw32-gcc |
Description (last modified by mojca (Mojca Miklavec))
The port ships gcc 3.4.5 from 2006, almost 8 years old. I would like to request updating to a more recent version. Sources for 4.8.1-4 are available on sourceforge at the moment.
http://sourceforge.net/projects/mingw/files/MinGW/Base/gcc/Version4/gcc-4.8.1-4/
Change History (8)
comment:1 follow-up: 5 Changed 13 years ago by mojca (Mojca Miklavec)
comment:2 Changed 13 years ago by mf2k (Frank Schima)
Cc: | landonf removed |
---|---|
Owner: | changed from macports-tickets@… to landonf@… |
Summary: | i386-mingw32-gcc → Update i386-mingw32-gcc to latest version |
Version: | 2.0.3 |
Fixed it. Note that Trac requires complete email addresses.
comment:3 Changed 12 years ago by cooljeanius (Eric Gallager)
Livechecking all the mingw ports gives the following result:
gl00b05047:/ root# port livecheck *mingw* Error: cannot check if i386-mingw32-binutils was updated (regex didn't match) Error: cannot check if i386-mingw32-gcc was updated (regex didn't match) i386-mingw32-libunicows seems to have been updated (port version: 1.1.1, new version: 1.1.2) Error: cannot check if i386-mingw32-runtime was updated (regex didn't match) Error: cannot check if i386-mingw32-w32api was updated (regex didn't match)
Looks like some livechecks need fixing here...
comment:5 Changed 11 years ago by cooljeanius (Eric Gallager)
Replying to mojca.miklavec.lists@…:
I'm sorry. I forgot to finish ticket name (it would make sense to use the word "update" in the name), but now I don't know how to change the name any more. Can somebody with sufficient rights fix this please?
Thank you.
Now that you have a @macports.org
email address you should be able to edit this ticket (mf2k may have already fixed the title issue you mentioned, but you may want to change the cc's or something...)
comment:6 Changed 11 years ago by mojca (Mojca Miklavec)
Description: | modified (diff) |
---|
comment:7 Changed 10 years ago by mojca (Mojca Miklavec)
See also #40174. Quite honestly I don't think that it's worth spending any time trying to get the old mingw working. It might be a lot more useful to get the MinGW-w64 working for both 32-bit and 64-bit. Designing the ports from scratch and keeping them up-to-date with the latest GCC release.
comment:8 Changed 8 years ago by mojca (Mojca Miklavec)
Resolution: | → wontfix |
---|---|
Status: | new → closed |
After five years I'm closing my own ticket as I don't think it's worth spending any time at all fixing issues with the old MinGW cross-compiler. It makes more sense to switch to MinGW-w64 completely.
I'm sorry. I forgot to finish ticket name (it would make sense to use the word "update" in the name), but now I don't know how to change the name any more. Can somebody with sufficient rights fix this please?
Thank you.