Default include path:
- before Sparsehash 2.0.1: /usr/include/google/sparsehash
- after Sparsehash 2.0.1: /usr/include/sparsehash
Even with the new include dir, the upstream wanted to keep the old include dir for backward compatibility propose. So, sparsehash 2.0.1 had "/usr/include/google" and "/usr/include/sparsehash".
However, version 2.0.1 had a bug: the backward compatibility was set to install in wrong directory. It was installing headers from "/usr/include/google/sparsehash" in "/usr/include/google". This issue was the subject of bug reported I opened in Sparshash site and it already solved.
This is no longer an issue in Sparsehash 2.0.2
Why it doesn't affect Archlinux users anymore? Because 1) I added a workaround using 'sed' to avoid this bug; and 2) Sparsehash in Archlinux was updated to 2.0.2.
- before Sparsehash 2.0.1: /usr/include/google/sparsehash
- after Sparsehash 2.0.1: /usr/include/sparsehash
Even with the new include dir, the upstream wanted to keep the old include dir for backward compatibility propose. So, sparsehash 2.0.1 had "/usr/include/google" and "/usr/include/sparsehash".
However, version 2.0.1 had a bug: the backward compatibility was set to install in wrong directory. It was installing headers from "/usr/include/google/sparsehash" in "/usr/include/google". This issue was the subject of bug reported I opened in Sparshash site and it already solved.
This is no longer an issue in Sparsehash 2.0.2
Why it doesn't affect Archlinux users anymore? Because 1) I added a workaround using 'sed' to avoid this bug; and 2) Sparsehash in Archlinux was updated to 2.0.2.
Support for Arch Linux users: http://forums.pcsx2.net/Thread-PCSX2-for-Arch-Linux