[Mingw-users] GCC-6.3 now available via mingw-get (was: GCC-6 and beyond)

[David Gressett]

on Monday, July 24, 2017 7:12 AM Keith Marshall wrote:
... snip ..

So, do any of you still have MinGW.org's GCC-4.8.1 installed?

... snip ...

Given the lack of response, I'm assuming that you either don't care ...

For me, 4.8.1 is long gone. I'm working on getting 6.4 and 7.1 going.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
MinGW-users mailing list
MinGW-***@lists.sourceforge.net

This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same. Disregard for the list etiquette may cause your account to be moderated.

_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users
Also: mailto:mingw-users-***@lists.sourceforge.net?subject=unsubscribe

[Jannick]

Given the lack of response, I'm assuming that you either don't care, or

you

don't expect to be affected. I've tried to keep the likely fallout as

painless as

possible, if you use the GUI interface to mingw-get, and you follow this

Thanks - this is helpful. Was just upgrading the MinGW32 suite to GCC6.

1) Update the catalogue, (via the "Installation" menu).

[snip]

5) Repeat step (2), to revisit the "GCC Upgrade Blockers" category; if
any packages there show up as "installed" again, (there should be a
few), then repeat step (3) to remove them again; (they serve only to
resolve dependencies during installation/upgrade, but will be in the
way of future upgrades; I plan to modify mingw-get, to remove them
automatically, following installation/upgrade processing, but for
the time being we must rely on manual removal).

Just as a separate note: libmingwex-0.dll appears to be a dependency to GCC6
which GCC6 complains about not to find upon compilation. The GUI interface
to mingw-get does not automatically download it by default, but a manual
installation fixes the issue.

Regards,
Keith.

Best,
J.


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
MinGW-users mailing list
MinGW-***@lists.sourceforge.net

This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same. Disregard for the list etiquette may cause your account to be moderated.

_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users
Also: mailto:mingw-users-***@lists.sourceforge.net?subject=unsubscribe

[Jannick]

Post by Jannick
Just as a separate note: libmingwex-0.dll appears to be a dependency
to GCC6 ...

You are correct[*]. It was not intended to be so, but is that so bad?
We have two choices: quickest, and easiest, would be to update the XML
catalogue, to include the dependency; alternatively, I could rebuild the

whole

kit and caboodle, to eliminate the dependency, which would take rather a
longer time.
Which would you prefer?

For this GCC version I would go with the easiest solution to change the XML,
of course - and given that the re-compilation sounds like more than a bunch
of lengthy work steps.

Regards,
Keith.

Best & thank you for all your efforts, Keith,
J.


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
MinGW-users mailing list
MinGW-***@lists.sourceforge.net

This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same. Disregard for the list etiquette may cause your account to be moderated.

_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users
Also: mailto:mingw-users-***@lists.sourceforge.net?subject=unsubscribe

[Jannick]

Post by Jannick

Post by Jannick
Just as a separate note: libmingwex-0.dll appears to be a dependency
to GCC6 ...

You are correct[*]. It was not intended to be so, but is that so bad?
We have two choices: quickest, and easiest, would be to update the XML
catalogue, to include the dependency; alternatively, I could rebuild the

whole

kit and caboodle, to eliminate the dependency, which would take rather
a longer time.
Which would you prefer?

For this GCC version I would go with the easiest solution to change the XML,
of course - and given that the re-compilation sounds like more than a bunch
of lengthy work steps.

Just a second: Would that mean that the compiled executables will be
dependent on .dlls even if linked with '-static' - if possible? I must admit
that in the beginning I was assuming that the mentioned .dll is required at
compile time only, but not at runtime. If this was true, this would not what
I wanted to opt for. Would you be able to shed some light on this?

Thanks,
J.


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
MinGW-users mailing list
MinGW-***@lists.sourceforge.net

This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same. Disregard for the list etiquette may cause your account to be moderated.

_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users
Also: mailto:mingw-users-***@lists.sourceforge.net?subject=unsubscribe

[Eli Zaretskii]

Date: Tue, 25 Jul 2017 11:37:20 +0100
You are correct[*]. It was not intended to be so, but is that so bad?
We have two choices: quickest, and easiest, would be to update the XML
catalogue, to include the dependency; alternatively, I could rebuild the
whole kit and caboodle, to eliminate the dependency, which would take
rather a longer time.
Which would you prefer?
$ mingw32-ldd dist/staged/libexec/gcc/mingw32/6.3.0/cc1.exe
dist/staged/libexec/gcc/mingw32/6.3.0/cc1.exe
+- ADVAPI32.DLL
+- KERNEL32.dll
+- libmingwex-0.dll
| +- msvcrt.dll
| +- msvcrt.dll
| +- ADVAPI32.DLL
| +- KERNEL32.dll

If you are going to leave cc1.exe dependent on libmingwex-0.dll,
please put that DLL under libexec, where cc1.exe lives, so that it is
not visible to "normal" MinGW builds, in case people don't want to
link against the DLL by default. That's what I do here.

Thanks.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
MinGW-users mailing list
MinGW-***@lists.sourceforge.net

This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same. Disregard for the list etiquette may cause your account to be moderated.

_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users
Also: mailto:mingw-users-***@lists.sourceforge.net?subject=unsubscribe