Re: Possible specs file error in MinGW GCC
Eli Zaretskii <eliz-mXXj517/[email protected]> Fri, 28 Feb 2020 09:18:51 +0200
| Newsgroups | gmane.comp.gnu.mingw.user |
|---|---|
| Message-ID | <[email protected]> |
> From: Keith Marshall <[email protected]> > Date: Wed, 26 Feb 2020 19:56:28 +0000 > > Explicitly specifying: > > $ gcc fubar.c -L ./foo.d -lmingwex > > (which effectively forces an extra scan of -lmingwex, *before* any of > the default library scans), is sufficient to overcome the problem. The > same effect may be achieved by modifying the GCC specs file, to move > -lmingwex before -lgcc; (it does not appear to be needed again, between > -lmoldname and -lmsvcrt); thus, the correct order would seem to be: > > -lmingw32 -lmingwex -lgcc -lgcc_eh -lmoldname -lmsvcrt > -ladvapi32 -lshell32 -luser32 -lkernel32 > > followed by repeated: > > -lmingw32 -lmingwex -lgcc -lgcc_eh -lmoldname -lmsvcrt > > I propose making this specs change, in the built-in specs for GCC-9.2, > and releasing this along with mingwrt-5.3. Thus, mingwrt-5.3 will be > dependent on this (rebuilt) GCC-9.2, or users will need to either link > -lmingwex explicitly, or make the requisite specs file change, if they > wish to use mingwrt-5.3 with any earlier version of MinGW-GCC. Sounds reasonable, thanks. _______________________________________________ MinGW-Users mailing list [email protected] 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.osdn.me/mailman/listinfo/mingw-users Also: mailto:[email protected]?subject=unsubscribe