> From: Keith Marshall <keith****@users*****> > Date: Wed, 15 Jul 2020 21:10:29 +0100 > > 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. FTR, I was building snapshots of what will shortly become GDB 10.1. > 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! Maybe it's worth reporting to gdb-p****@sourc*****, as a potential bug. if the GDB developers have good reasons not to support this option, they will tell; otherwise I think it's reasonable to expect it be supported, given the common configuration machinery. > 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. I think the canonical ways of doing this is to set CPPFLAGS when running 'configure', i.e. CPPFLAGS=-I/mingw ./configure ... Did you try that?
Fork