cone FTBFS in karmic

Seems like a missing build dep on libtool

assigning to myself

Regards

Its still FTBFS

http://launchpadlibrarian.net/30931963/buildlog_ubuntu-karmic-i386.cone_0.77-2ubuntu1_FAILEDTOBUILD.txt.gz

The macros seem to rely on implicit conversion from void * to char * which is permitted in C but not CPP.

Unassigning

Regards

Sorry its const void and essentially a gcc problem i think...

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.

Okay michael

Reporting to debian

and unassigning

Regards

Hi,

Here is the corresponding debdiff. This compilation error has been solved in latest cone version. I've opened a bug report in Debian requesting the upgrade of cone, so that we can sync cone in the next development cycle.

Thanks fabrice...

hm... the const_cast seems pretty ugly at this place (why not just modify the std::string using std::string methods?), however as this fix is in 0.79, I'm ok with it, test-buliding.

This bug was fixed in the package cone - 0.77-2ubuntu1

---------------
cone (0.77-2ubuntu1) karmic; urgency=low

  * debian/control: added build dependency on libtool (thanks Bhavani Shankar)
    (LP: #420303)
  * debian/patches/gcc_4.4.diff: fix compilation errors with gcc 4.4
    (retrofitted from version 0.79)

 -- Fabrice Coutadeur <email address hidden> Tue, 15 Sep 2009 04:34:52 +0000

uploaded, thanks!