Cherry-picking 64fe266 into the 1.6 branch?

Raphael Kubo da Costa rakuco at FreeBSD.org
Sat Jan 18 18:38:50 UTC 2014


Hi all,

I was wondering if there are any plans to get commit 64fe266 ("Remove
google sparse/dense hash code.") into the 1.6 branch: when packaging
KDevelop 4.6.0 for FreeBSD, I've noticed that the sparseconfig.h always
assumes libstdc++ is being used and that its implicit includes end up
including hash_fun.h (or backward/hash_fun.h depending on your
libstdc++). This breaks recent FreeBSD versions which only ship libc++
by default, and would be easily solved if that commit made it into the
stable branch.

For now, I'm probably going to backport that commit into our package,
but it would be good to get some confirmation that this commit alone is
enough and/or that this is planned.

Cheers.



More information about the KDevelop-devel mailing list