Use '::iterator' instead of '::const_iterator' on environ.c (and fix breakage on...
authorSergio Durigan Junior <sergiodj@redhat.com>
Tue, 20 Jun 2017 13:33:53 +0000 (09:33 -0400)
committerSergio Durigan Junior <sergiodj@redhat.com>
Tue, 20 Jun 2017 13:33:53 +0000 (09:33 -0400)
commit96160d605128658378af73bb62732d1cbfa73d8a
tree96b5db6aac4eafa9f808f563cee51c74c71b73d1
parent9a6c7d9c021cfeb290d76584db7a01e57e7c3d4e
Use '::iterator' instead of '::const_iterator' on environ.c (and fix breakage on early versions of libstdc++)

Even though C++11 supports modifying containers using a const_iterator
(e.g., calling the 'erase' method of a std::vector), early versions of
libstdc++ did not implement that.  Some of our buildslaves are using
these versions (e.g., the AArch64 buildslave uses gcc 4.8.8), and my
previous commit causes a breakage on them.  The solution is simple:
just use a normal iterator, without const.

gdb/ChangeLog:
2017-06-20  Sergio Durigan Junior  <sergiodj@redhat.com>

* common/environ.c (gdb_environ::unset): Use '::iterator' instead
of '::const_iterator'.
gdb/ChangeLog
gdb/common/environ.c
This page took 0.02402 seconds and 4 git commands to generate.