aboutsummaryrefslogtreecommitdiff
path: root/gold
diff options
context:
space:
mode:
authorSergio Durigan Junior <sergiodj@redhat.com>2017-06-20 09:33:53 -0400
committerSergio Durigan Junior <sergiodj@redhat.com>2017-06-20 09:33:53 -0400
commit96160d605128658378af73bb62732d1cbfa73d8a (patch)
tree96b5db6aac4eafa9f808f563cee51c74c71b73d1 /gold
parentC++ify gdb/common/environ.c (diff)
downloadbinutils-gdb-96160d605128658378af73bb62732d1cbfa73d8a.tar.gz
binutils-gdb-96160d605128658378af73bb62732d1cbfa73d8a.tar.bz2
binutils-gdb-96160d605128658378af73bb62732d1cbfa73d8a.zip
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'.
Diffstat (limited to 'gold')
0 files changed, 0 insertions, 0 deletions