Time for a MinGW-GDB Upgrade?
Keith Marshall <[email protected]> Wed, 15 Jul 2020 21:10:29 +0100
| Newsgroups | gmane.comp.gnu.mingw.user |
|---|---|
| Organization | MinGW.org Project |
| Message-ID | <[email protected]> |
In message
https://osdn.net/projects/mingw/lists/archive/users/2020-July/000584.html,
Eli Zaretskii indicated that, pursuant to resolution of an issue with
the build of GCC-9.2.0, (subsequently resolved), GDB can be readily
built with MinGW. This has prompted me to review the release status of
MinGW-GDB, (currently at GDB-7.6.1).
Unfortunately, my own experience of building, from GDB-9.2 sources, has
been less positive than Eli's; the first problem I encounter is:
In file included from ../../src/gdb-9.2/bfd/archive.c:134:
../../src/gdb-9.2/bfd/sysdep.h:185:11: fatal error: libintl.h:
No such file or directory
185 | # include <libintl.h>
| ^~~~~~~~~~~
compilation terminated.
This arises because, rather than having libintl in my default GCC search
path, I have it in a /mingw staging path, whence my GCC build procedure
accesses it via a "--with-libintl-prefix=/mingw" configuration option.
Given that GDB's configuration procedure has every appearance of being a
cobbled-together derivative of GCC's, I specified this same option in my
GDB configuration, but sadly, it has no effect! (To be fair, it is not
mentioned in GDB documentation, so likely it isn't supported); however,
CPPFLAGS, which *is* documented, *should* offer a work around for this
issue, but doesn't, because the fragmented configuration process utterly
fails to propagate it to subsidiary configurations, and thus, it does
not deliver its documented behaviour where it matters.
I can kludge around this GDB bug, by passing "CPPFLAGS=-I/mingw" through
the process environment[1], when running make:
CPPFLAGS=-I/mingw make
but the alternative, (and possibly more natural):
make CPPFLAGS=-I/mingw
does *not* work; in this latter case, CPPFLAGS does not propagate to the
subdirectory makefiles.
[1] Of course, I could also just move the libintl headers and libraries
into the compiler's default search path, but I would prefer not to do
so; notwithstanding that I can kludge around this, (and thus move on to
the next issue, which I'll address in a follow-up post), this is a GDB
bug, which IMO merits upstream attention.
--
Regards,
Keith.
Public key available from keys.gnupg.net
Key fingerprint: C19E C018 1547 DE50 E1D4 8F53 C0AD 36C6 347E 5A3F
_______________________________________________
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
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEwZ7AGBVH3lDh1I9TwK02xjR+Wj8FAl8PYrcACgkQwK02xjR+ Wj+PSQ/8CMKZOfEoA2jH8PLV65pJUYTjPkR4m0Q/KwZOZWmqCfmCkyE4q2Nv8B2s 6qp/HNBjh5qvSiDKMIc9LnJD2hYE6jPWT2OZ7xEE5+ffL/emHS6795Y50ravPHxN +K9IrwRZ4VPN34lctgzbzxRa6NRv1Ch1/dDirNqjgmN9TEVVNC2pEn+amwvKfXMJ kPLcaon7BYXNzeAZjszKpPvxbO+OyF1I7th5y7wr0yykmM2jRf9YmcuV1AmuWYBR t2F2Et38ypjgvYQdyI3U3NvZTwtfaHRQYbni/UGpmuUQBZzzcmllM/THflxlFPc6 eWSibEEHGycEeqJcUPnRQWWyCBtkB2H/bucSDGItJ1tp+BEyGIIAqf9ejLg9MqOE 2T6YlsAPtP+kKsj37UIsy9n3hkGDS7IDaWocZet/UaK37M8IDkSjhv7w/R9XPpJQ jWAA1aIwg15CSzPx7iZBa7kC+dncTYDwbtXdrQjMvbIwHsDuHWSmpqRxz84NE6MB UDrpLxVcym6fz/2CP8PCKXRP5T/MvZuURMjruNQw+uVaPQ09CFKaEwYxXDI3zRrf P9ZRbmuws42uocf1e0uNCRbpbPzkpsZBeO/jjKF2ih7doiqo9gRCM8izEWuWAmX3 lges9bUFvXsPIwBSj9JFliA+SMMAq8EH6OKRFWPwCSo9psPsBjA= =UQLs -----END PGP SIGNATURE-----