I would like to add sys-libs/libstdc++-v3-bin-3.3.6 to portage. This would be a ppc64 only package and would 'provide' virtual/libstdc++-3.3. The problem we have on ppc64 is this: libstdc++-v3 won't compile using gcc 4 (first seen in bug #97977). As a result we cannot compile neither gcc-3.4.x nor libstdc++-v3 on ppc64. Unfortunately we need libstdc++-v3 for the java binary packages from IBM. As this only affects ppc64 I would like to bump this into stable before 2007.1 snapshot. As a result we can mask gcc-3 and sys-libs/libstdc++-v3 in the upcoming 2007.1 profiles for ppc64, since both packages do not compile with gcc-4. toolchain: are you confident with this?
Created attachment 132995 [details] libstdc++-v3-bin-3.3.6.ebuild the tarball sits currently here [1], but I would move it on the mirrors, when adding this package. [1] http://dev.gentoo.org/~corsair/libstdc++-v3-bin-ppc64-3.3.6.tbz2
Created attachment 132996 [details] libstdc++-3.3.ebuild.patch (virtual/libstdc++) patch for the virtual
Created attachment 132998 [details] libstdc++-3.3.ebuild.patch (virtual/libstdc++) first patch was the wrong way around...
Created attachment 132999 [details] libstdc++-v3-bin-3.3.6.ebuild nah.. forgot the licence and the RDEPEND. As this is a binary package it depends on sys-libs/glibc and not virtual/libc.
what is wrong with just using the existing libstdc++-v3 package
(In reply to comment #5) > what is wrong with just using the existing libstdc++-v3 package it won't compile. see bug #97977. Or do you mean "install the binary package with sys-libs/libstdc++-v3-3.3.6, instead of adding a separate package"?
then why not fix libstdc++-v3 ?
(In reply to comment #7) > then why not fix libstdc++-v3 ? because I don't have the knowledge and upstream won't do it: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23158
vapier: are you now OK with adding this?
vapier: ping, I would like to get this into 2007.1 tarball if possible.
release: I would like to have this in 2007.1, so we have a useable jdk/jre (java is a binary package that depends on libstdc++-v3). I don't want to add this, unless toolchain says it's OK.
Well, this has really no hope of making it into the release unless you can get it into the tree $NOW and get it ready for stable *before* the end of the month.
Unless noone has serious reasons agains this I'll add it to portage at the end of next week. I plan to stabilize after a few days, as I've used this quite some time now on various machines.
I hope "by the end of next week" means "by Friday" of this week, otherwise, it isn't likely to make it into the release.
It's in the tree now (~ppc64) as noone gave a reason not to do so.
stable on ppc64
Great. What other changes do I need to pull into the release snapshot? Were there any other packages changed? I would assume at least a couple Java packages, or possibly the virtuals?
sys-libs/libstdc++-v3-bin and updated virtual/libstdc++ needs to be in the snapshot. thanks.
Done... thanks...
