Cherry-picking 64fe266 into the 1.6 branch?

Milian Wolff mail at milianw.de
Sat Jan 18 18:46:47 UTC 2014


On Saturday 18 January 2014 20:38:50 Raphael Kubo da Costa wrote:
> 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.

Yes that could be backported. As far as I can see it should even uphold binary 
compatibility.

I'll do that now.

Bye
-- 
Milian Wolff
mail at milianw.de
http://milianw.de


More information about the KDevelop-devel mailing list