From: Keith M. <kei...@us...> - 2017-07-31 22:35:11
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 31/07/17 17:35, Earnie via MinGW-users wrote: >> _Operating System:_ >> >> Windows 10 > > New OS ... > >> _GCC Version:_ >> >> Reading specs from C:/Program Files (x86)/AEgis >> Technologies/acslX/mingw32/bin/../lib/gcc/mingw32/3.4.2/specs > > Old GCC ... I just closed (as invalid) https://sourceforge.net/p/mingw/bugs/2268/, which exhibits a similar issue, (also referring to gcc-3.4.2). I concur with Earnie; if you insist on continuing to use such an ancient version of GCC, then you are (mostly) on your own; none of the supporting (development) library packages hosted within our FRS are compatible with any pre-GCC-4.x release, (with x >= 5, I believe). Current MinGW.org GCC release is GCC-6.3.0 - -- Regards, Keith. Public key available from keys.gnupg.net Key fingerprint: C19E C018 1547 DE50 E1D4 8F53 C0AD 36C6 347E 5A3F -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iQIcBAEBAgAGBQJZf7CWAAoJEMCtNsY0flo/8KMP/A7Sj17y/h1ZlFGisr4F5563 Q00+8hsf5T8oWoxBSqT59DL6jgzIeGAWnZmIApKSKQSVb3DaHptSCS9+h9d1Kewi DdoK23avygJwirx5NwYixZ6UiNXZvvA4wDw1Dkfw6blFcLsb7NbaMRIDhXzvX55s Vr8REZLgR8avTSuMSrufBH6qHfC4qkvJ/2l/Ppc/126111iUONAW542M1/pJFKTf ykszsA6q2+QWZ3JZjk7+GGEx3uc0UOf623NyZw8L10zh+KDKBQwT5uf1GngpG7Jf RQ6R9EfNbMwkJGHkpRQPJQ19muuo2wKxyrXWwag5vlwwmcDOJgRJxsaLBWkcs+UG eX3GxQl/iF4WkvhGEGgCiFObyyNz+hqGvtj8GpQpqChY5UySgMQaiIvU9tD5gu+Z j/u8RcvLhOAJIsZyH9aktwWX4WeV9cLwVcc4fu59g8wd05W5FFu5FHf0OrlEbR/9 BZ+kXqq8t9Rk6ty/3foxVyFHrQlgNkzOv6n75k3o+vZdGpcCjcBF2gTxag5Kpgtk vTQ3TviInc5yOnARaxqOvSVNnz4+2nHl+qlEX4L9hi2PxInOcSUp96Fz4iN7qHBZ l6Pk3UcWhgHz7SPOFEygcZOHZA61rNLRwvASGf5tKFFEYo0ViS6hXvbM0fMrAaTQ QiITjqsh/TKLNlHuuKOE =EWAQ -----END PGP SIGNATURE----- |