It's not a gcc problem, but a bug in the code:
libmaildir/maildiradd.C:168
memcpy(strrchr(newname.c_str(), '/')-3, "cur", 3);
c_str() returns a const char* (i.e. read-only), strrchr() on a const char*
returns also a const char*
but memcpy expects to get there a pointer to a read-write location
That's the problem gcc complains about. From a look at the code, this
code needs to be changed to do the modification on newname (C++ string)
directly and not on its C representation.
--
cone FTBFS in karmic
https://bugs.launchpad.net/bugs/420303
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
--
universe-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/universe-bugs
