Hi. gdb recently updated gnulib to
GNULIB_COMMIT_SHA1="0cda5beb7962f6567f0c4e377df870fa05c6d681"
This caused a build failure here at AdaCore, where we are using a
relatively recent GCC (11.2) on an rhES 7 host:
CC libgnu_a-openat-proc.o
In file included from /usr/include/string.h:633,
On this system:
$ uname -r
2.6.32-754.35.1.el6.x86_64
... the gnulib in gdb failed to build:
CC glob.o
../../../binutils-gdb/gnulib/import/glob.c: In function ‘next_brace_sub’:
../../../binutils-gdb/gnulib/import/glob.c:89: error: expected declaration
specifiers before ‘__THROWNL’
[...]
> "Bruno" == Bruno Haible writes:
Bruno> I updated the documentation accordingly:
Thank you.
Tom
| 5 +
lib/stdlib.in.h | 3 ++-
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/ChangeLog b/ChangeLog
index 8ef956b36..67091fb1e 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2018-10-01 Tom Tromey
+
+ * lib/stdlib.in.h: Include for mkostemp and mkostemps
> "Sergio" == Sergio Durigan Junior writes:
> Another possibility that may be simpler for GDB, is to change its
> configure.ac files to require C99 or later everywhere. At this point
> it's more trouble than it's worth to tweak source code or makefiles to
> cater to compilers operatin
> "Sergio" == Sergio Durigan Junior writes:
>>> "CC=$(CC)" \
>>> "CFLAGS=$(CFLAGS)" \
>>> "CXX=$(CXX)" \
>>> "CXX_DIALECT=$(CXX_DIALECT)" \
>>> "CXXFLAGS=$(CXXFLAGS)" \
>>> ...
>>> Which ends up overriding gnulib's CC/CXX variables. That's why we don't
>>> see the "-std=gnu11" there.
>> Ma
>>>>> "Paul" == Paul Eggert writes:
Paul> On 11/20/2013 07:09 AM, Tom Tromey wrote:
>> However, after some exploration I discovered that I could eliminate the
>> gethostname error by dropping the strstr and strerror modules.
Paul> Thanks, I assume
>>>>> "Tom" == Tom Tromey writes:
Tom> In particular one part of gdb uses gethostname. So, I had to include
Tom> the gethostname module.
The situation is weirder than I thought.
The reason I tried to import the gethostname module is that we were
seeing this err
I tried to use gnulib more in gdb, but ran into issues with the mingw
port.
In particular one part of gdb uses gethostname. So, I had to include
the gethostname module.
But, if I include that module, then the gnulib unistd.h can wind up
including , which pulls in a lot of definitions that confli
> "Joel" == Joel Brobecker writes:
Joel> I am not sure I understand what you mean. My suggestion was to
Joel> have libiconv and gnulib use the same value for EILSEQ. As for
Joel> gnulib, it uses an arbitrary value that's fairly large, compared
Joel> to typical values, so it should be distinc
> "Jim" == Jim Meyering writes:
Jim> That is correct. It is a feature of gdb-7.0 and newer.
Jim> You can inspect (watch/break-at/etc.) the same address and expect it
Jim> to refer to the same memory location in multiple invocations.
Jim> This makes gdb's command-line history even more useful
11 matches
Mail list logo
