http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57454
--- Comment #8 from Dmitry ---
Yes, you was right. Completely right.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57454
Marek Polacek changed:
What|Removed |Added
Status|CLOSED |RESOLVED
Resolution|WONTFIX
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57454
Dmitry changed:
What|Removed |Added
Status|RESOLVED|CLOSED
Resolution|INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57454
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57454
Dmitry changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57454
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment #
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57454
--- Comment #2 from Dmitry ---
(In reply to Jonathan Wakely from comment #1)
> This is not a GCC bug, the error you get is not even from GCC, it's from the
> linker, but the problem is almost certainly due to you not linking to a
> required librar
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57454
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---