Actually, it's not as simple as making gcc2 or gcc4 subdirs...
If you're on a gcc2hybrid (where the base Haiku is compiled with gcc2,
but contains alternative gcc4 libraries), then all gcc2 libs would be
in just lib - while gcc4 c++ libs (since only C++ compiled stuff
causes the ABI issue) go into a gcc4 sub dir... whereas if you're on a
gcc4hybrid all the gcc4-compiled libs go into just lib, while gcc2 c++
compiled libs go into a gcc2 subdir.
Thus, you can't just always put stuff in gcc2 or gcc4 - but rather you
must evaluate it based on the target version of Haiku. This makes it
hard to anticipate from the porter point of view.
Any ideas?
- Urias
