When I first attempted to emerge STLport, it failed because the ebuild was trying to make -f in the wrong dir. After fixing that, I noticed that the defined path for the standard c++ include files was wrong for gcc-3.2. I did some research and discovered that this was a problem for gcc-3.1 as well. I motified the original patch so that it fixes the path for gcc-3.2 as well. Finally, I wasn't satisified with level of optimization provided by the library [this is gentoo after all ;-)]. So I have submitted another patch to fix the ebuild so that the flags in make.conf get passed to the compiler. So you will find 2 patches and a modified ebuild attached to adress all of these issues.
Created attachment 2874 [details, diff] Patch for gcc-3.1 and gcc-3.2 support
Created attachment 2875 [details, diff] Patch for user defined optimizations a.la. make.conf
Created attachment 2876 [details, diff] ebuild for the aforementioned patches + fix for make
you kickass, applying.
I think an option we should consider, is maybe adding some way to get the location to the c++ include files in some generic way. Dunno how yet though.
I don't think that is possible with out massive changes to how the system is built. You're actually supposed to edit that file for your platform, since this package contains no configure scripts [which work][this is intentional according to the author]. This is the best way to do it, unless someone is willing to get the upstream provider to reimplement the autotools.
Hmm, ok. Guess we will just have to keep on patching it.
