On 17/07/2020 11:44, Eli Zaretskii wrote: >> ... of GDB's configuration (in subdirectories) is deferred until >> the top level "make" is run, and the top level configure's notion of >> CPPFLAGS isn't propagated, through the "make" phase, to the subdirectory >> "configure" runs. > > That sounds like another bug, because CFLAGS and CXXFLAGS set the same > way _are_ propagated. And "/configure --help" at top level does > mention all of the variables, including CPPFLAGS and CFLAGS/CXXFLAGS. > FWIW, I set CFLAGS and CXXFLAGS (using the archaic method) all the > time when I build GDB. Okay. I raised the issue on gdb-p****@sourc*****, as you suggested: https://sourceware.org/pipermail/gdb-patches/2020-July/170547.html Meanwhile, using the kludged work-around, as I previously described, allows me to move on to the next problem: CXX source-cache.o ../../src/gdb-9.2/gdb/source-cache.c:37:10: fatal error: srchilite/sourcehighlight.h: No such file or directory 37 | #include <srchilite/sourcehighlight.h> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. make[2]: *** [Makefile:1656: source-cache.o] Error 1 Now, this should not have happened: there is a configuration test for availability of source-highlight, which should have conditionally marked this section of code for omission, (because the source-highlight API is not present in my MinGW tree). Yet another GDB configuration bug, which I will also report on gdb-patches ... I can even offer a one-line patch to correct it. That said, I note that you, Eli, do build your GDB with source-highlight support. How much of a sacrifice would it be, if I omit it? -- Regards, Keith. Public key available from keys.gnupg.net Key fingerprint: C19E C018 1547 DE50 E1D4 8F53 C0AD 36C6 347E 5A3F -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: <https://lists.osdn.me/mailman/archives/mingw-users/attachments/20200718/e8215068/attachment-0001.sig>
Fork