On Mon, Apr 12, 2010 at 6:57 AM, Mark Knecht <[email protected]> wrote:
> ...is not so good actually. Certainly not the way I'd want others to
> experience Gentoo.
>
> OK, the ~amd64 upgrade to @system was easy and relatively painless.
> The documents were fairly clear. There are things to learn, and old
> friends like rc-update and df look different, but it worked and didn't
> take long - less than an hour to reboot including editing - so that's
> good.
>
> Unfortunately, simply allowing all environments & apps on the system
> to go ~amd64 isn't working out as nicely.
>
> 1) xfce4 had one build failure. I masked it and the build finished.
> xfce starts and seems to mostly work, but I get no wallpaper and the
> right click for a menu on the desktop doesn't work. It's usable, but
> clearly 'not stable'.
Hi,
I'm using ~amd64 for my whole system (for years). I have a similar
system to yours, but only a Core i7 920, :) and at the moment every
package on my system builds fine.
Which package failed? Which profile and GCC are you using? I just
emerged xfce4-meta and everything worked. Here's my GCC, profile and
xfce versions (I also use unmasked portage):
[ebuild R ] sys-devel/gcc-4.4.3 USE="fortran gcj graphite gtk
mudflap (multilib) nls nptl objc objc++ objc-gc openmp (-altivec)
-bootstrap -build -doc (-fixed-point) (-hardened) (-libffi) -multislot
(-n32) (-n64) -nocxx -test -vanilla" 0 kB
$ sudo gcc-config -l
[1] x86_64-pc-linux-gnu-4.4.3 *
$ sudo eselect profile show
Current make.profile symlink:
default/linux/amd64/10.0/desktop
My cflags:
CFLAGS="-march=native -O3 -floop-interchange -floop-strip-mine
-floop-block -ggdb -pipe"
CXXFLAGS="${CFLAGS}"
LDFLAGS="-Wl,--as-needed"
$ emerge -vp xfce4-meta
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild N ] xfce-base/libxfce4util-4.7.1 USE="-debug" 0 kB
[ebuild N ] dev-util/xfce4-dev-tools-4.7.2 0 kB
[ebuild N ] x11-themes/xfce4-icon-theme-4.4.3 0 kB
[ebuild N ] x11-themes/gtk-engines-xfce-2.6.0 0 kB
[ebuild N ] xfce-base/xfconf-4.7.2 USE="perl -debug -profile" 0 kB
[ebuild N ] xfce-base/exo-0.3.106 USE="hal libnotify python -debug" 0 kB
[ebuild N ] xfce-base/libxfce4menu-4.6.1 USE="-debug" 0 kB
[ebuild N ] xfce-base/libxfcegui4-4.6.3 USE="startup-notification
-debug -glade" 0 kB
[ebuild N ] xfce-base/xfce4-panel-4.6.2-r1
USE="startup-notification -debug" 0 kB
[ebuild N ] xfce-base/xfce-utils-4.6.1 USE="dbus lock -debug" 0 kB
[ebuild N ] xfce-base/xfwm4-4.6.1 USE="startup-notification
xcomposite -debug" 0 kB
[ebuild N ] xfce-base/xfce4-settings-4.6.3-r1 USE="keyboard
libnotify -debug -sound" 0 kB
[ebuild N ] xfce-base/xfce4-session-4.6.1-r1 USE="-debug -fortune
-gnome -gnome-keyring -profile" 0 kB
[ebuild N ] xfce-base/thunar-1.0.1 USE="dbus exif hal pcre
startup-notification trash-plugin -debug -doc -gnome -test" 0 kB
[ebuild N ] xfce-base/xfdesktop-4.6.1-r1 USE="branding
menu-plugin thunar -debug -doc" LINGUAS="-be -ca -cs -da -de -el -es
-et -eu -fi -fr -he -hu -it -ja -ko -nb_NO -nl -pa -pl -pt_BR -ro -ru
-sk -sv -tr -uk -vi -zh_CN -zh_TW" 0 kB
[ebuild N ] xfce-base/xfce4-meta-4.6.1 USE="session -minimal" 0 kB
The xfce wallpaper thing sounds like what I experienced with xfce
during the jpeg-6-to-7 upgrade process. At the time, jpeg was not
slotted and there was jpeg-compat for programs that were incompatible
with jpeg-7. Now we have jpeg-8 as well, and 6/7/8 are in slots, so
maybe the solution is different. Back then, I unmerged and masked
jpeg-6, revdep-rebuild everything that depended on jpeg so that it was
built against jpeg-7 and then everything was fine. (Maybe there was a
gtk+ patch I had to apply on day 0, but that was long ago made
obsolete by newer versions of gtk+ in portage)
> 2) gnome-2.28 simply doesn't build.
I'm not a gnome user but I can try this if you want (135 packages to
emerge in my case), or if you have more specific info about which part
doesn't build I can try only the specifics.
> 3) I'm currently left with lots of things in emerge @preserved-rebuild
> that don't build. emerge -DuN @world is not clean.
Maybe you can unmerge those packages, allowing emerge to get rid of
the preserved libs, then emerge world to bring those packages back.
