Greg is correct. I ran into the bug and accidentally submitted it, and it let me here. The problem was I set up update-alternatives, and tried to run it under gcc and g++ 4.8. When I went back to gcc and g++ 5.2.1, the bug went away.
Greg is correct. I ran into the bug and accidentally submitted it, and it let me here. The problem was I set up update- alternatives, and tried to run it under gcc and g++ 4.8. When I went back to gcc and g++ 5.2.1, the bug went away.