Hello, we ran into some problems with having gcc 4.1 and glibc 2.4 unmasked on ppc64/32bit userland. see bug #139151 I think there are no changes needed for ppc64/64ul in 2006.1 profile. so copying it would be sufficient. (we might want to add gcc41 profiles but that would be extra foo. we need to get stable fixed!) on ppc64/32ul we just need changes in 'packages' file in 2006.1 profile. Something like this: ############################################################################## diff -ruN 2006.0/32bit-userland/packages 2006.1/32bit-userland/packages --- 2006.0/32bit-userland/packages 2006-06-30 17:06:35.000000000 +0000 +++ 2006.1/32bit-userland/packages 2006-07-04 14:25:54.000000000 +0000 @@ -4,8 +4,6 @@ *sys-devel/gcc-powerpc64 *sys-apps/setarch ->=sys-devel/gcc-3.4.4-r1 ->=sys-libs/glibc-2.3.5-r2 -<sys-devel/gcc-4 -<sys-libs/glibc-2.4 - +>=sys-devel/binutils-2.16.1 +>=sys-devel/gcc-4.1.1 +>=sys-libs/glibc-2.4 ############################################################################## dostrow is currently moving so he could not add the new profiles until next week, so I propose copying 2006.0 to 2006.1 and apply the above patch ASAP. Comments?
I've found no other way to emerge gcc-4 and glibc-2.4 (package.unmask doesn't change anything), which keeps my toolchain in a bad state with no possibility to repair it (gcc-3.4.6 and glibc-2.4, portage wants to emerge glibc-2.3.6,but can't downgrade glibc). This bug being kept unresolved causes me big trouble. If you don't want to make this change quickly, could you mask the glibc-2.4 and gcc-2.4 packages in the 2006.0 profile using the package.mask file instead of the packages file ? It would allow to unmask them.
(In reply to comment #1) > > If you don't want to make this change quickly, could you mask the glibc-2.4 and > gcc-2.4 packages in the 2006.0 profile using the package.mask file instead of > the packages file ? It would allow to unmask them. > Answer to myself: this part is stupid ! I misunderstood the package.mask package. (thanks to mabi on #gentoo-ppc )
(In reply to comment #1) > I've found no other way to emerge gcc-4 and glibc-2.4 (package.unmask doesn't > change anything), which keeps my toolchain in a bad state with no possibility > to repair it (gcc-3.4.6 and glibc-2.4, portage wants to emerge glibc-2.3.6,but > can't downgrade glibc). The workaround to override the profile (tahnks SpanKY !) is to create the file /etc/portage/profile/packages with the following lines -<sys-libs/glibc-2.4 -<sys-devel/gcc-4
dostrow added 2006.1 profiles.
newer click on the wrong place..
marking as FIXED
closing
