I want to `emerge update world` after having done succesful `emerge update system` to move from gentoo 1.2 to 1.4 gtk+-1.2.10-r9 finished fine (I assume, because emerge recompiled some other applications afterwards), but pongo didn't, have a look at this; ---schnipp--- /usr/include/pango-1.0/pango/pango-font.h:123: warning: data definition has no t ype or storage class In file included from /usr/include/pango-1.0/pango/pango.h:25, from ../gdk/gdktypes.h:33, from ../gdk/gdkcolor.h:4, from ../gdk/gdk.h:30, from ../gtk/gtkdnd.h:30, from gtktreednd.h:24, from gtkliststore.c:25: /usr/include/pango-1.0/pango/pango-attributes.h:168: parse error before `weight' make[3]: *** [gtkliststore.lo] Error 1 make[3]: Leaving directory `/var/tmp/portage/gtk+-2.0.6-r2/work/gtk+-2.0.6/gtk' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/gtk+-2.0.6-r2/work/gtk+-2.0.6/gtk' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/gtk+-2.0.6-r2/work/gtk+-2.0.6' make: *** [all-recursive-am] Error 2 ---schnapp--- the update list of `emerge update world` is this: ---schnipp--- [ebuild U ] net-www/opera-static-6.03 [ebuild U ] sys-kernel/xfs-sources-2.4.19-r1 [ebuild U ] dev-libs/openssl-0.9.6g [ebuild U ] net-print/cups-1.1.16 [ebuild U ] net-fs/samba-2.2.5-r1 [ebuild U ] app-arch/unzip-5.50 [ebuild U ] dev-lang/nasm-0.98.34 [ebuild U ] media-libs/freetype-2.1.2-r1 [ebuild U ] x11-libs/gtk+-1.2.10-r9 [ebuild U ] media-libs/libvorbis-1.0-r1 [ebuild U ] media-sound/esound-0.2.29 [ebuild U ] media-video/mplayer-0.90_pre8 [ebuild U ] net-www/lynx-2.8.4.1c [ebuild U ] app-cdr/cdrtools-1.11.34 [ebuild N ] x11-libs/pango-1.0.4-r1 [ebuild N ] dev-libs/atk-1.0.3-r1 [ebuild U ] x11-libs/gtk+-2.0.6-r2 [ebuild U ] app-admin/gkrellm-2.0.2 [ebuild U ] media-libs/libmng-1.0.4 [ebuild U ] x11-libs/qt-3.0.5-r2 [ebuild U ] kde-base/kde-env-3-r2 [ebuild U ] app-admin/fam-oss-2.6.9 [ebuild U ] dev-libs/libxml2-2.4.24 [ebuild U ] dev-libs/libxslt-1.0.20 [ebuild U ] app-text/ghostscript-7.05.5 [ebuild U ] kde-base/arts-1.0.4 [ebuild U ] kde-base/kdelibs-3.0.4 [ebuild U ] kde-base/kdesdk-3.0.4 [ebuild N ] dev-perl/ExtUtils-MakeMaker-6.03-r1 [ebuild N ] dev-perl/Test-Harness-2.24 [ebuild N ] dev-perl/Test-Simple-0.42 [ebuild U ] dev-perl/Storable-2.04 [ebuild U ] media-gfx/imagemagick-5.4.7-r2 [ebuild U ] media-video/dvdrip-0.46 [ebuild U ] gnome-extra/mc-4.6.0_pre1 [ebuild U ] net-misc/dhcp-3.0-r4 [ebuild U ] media-libs/xpm-3.4k-r1 [ebuild N ] app-editors/vim-core-6.1-r2 [ebuild U ] app-editors/vim-6.1-r15 ---schnapp---- what had been succesfully update by `emerge update system` was: ---schnipp--- [ebuild U ] sys-libs/glibc-2.2.5-r7 to / [ebuild U ] sys-libs/ncurses-5.2-r6 to / [ebuild U ] sys-apps/bash-2.05a-r3 to / [ebuild U ] dev-lang/tk-8.3.3-r2 to / [ebuild U ] dev-lang/python-2.2.1-r5 to / [ebuild U ] sys-apps/debianutils-1.16.3 to / [ebuild U ] sys-apps/fileutils-4.1.11 to / [ebuild U ] sys-apps/portage-2.0.38 to / [ebuild U ] sys-apps/baselayout-1.8.3 to / [ebuild U ] sys-devel/perl-5.6.1-r7 to / [ebuild U ] app-editors/nano-1.0.9 to / [ebuild U ] net-misc/rsync-2.5.5-r1 to / [ebuild U ] sys-apps/diffutils-2.8.4 to / [ebuild U ] sys-apps/e2fsprogs-1.29 to / [ebuild U ] sys-apps/file-3.39 to / [ebuild U ] sys-apps/hdparm-5.2-r3 to / [ebuild U ] sys-apps/iptables-1.2.7a to / [ebuild U ] sys-apps/modutils-2.4.19 to / [ebuild U ] sys-apps/reiserfsprogs-3.6.3 to / [ebuild U ] sys-apps/sed-3.02.80-r4 to / [ebuild U ] sys-apps/sh-utils-2.0.15 to / [ebuild U ] sys-apps/pam-login-3.7 to / [ebuild U ] sys-apps/tar-1.13.25-r3 to / [ebuild U ] sys-apps/textutils-2.1 to / [ebuild U ] sys-apps/util-linux-2.11u to / [ebuild U ] sys-devel/bison-1.35 to / [ebuild U ] sys-devel/make-3.79.1-r5 to / ---schnapp--- I hope this is enough information for helping solving the problem, thanks. greetings, Sascha
Pango has nothing todo with gtk-1.2. Try to clean out pango and atk (emerge -C), re-emerge them and then emerge gtk2 (gtk+-2.0.6).
pango and atk aren't installed, yet. they only belong to the update world list to be installed. but have a look at the order: ---schnipp--- [ebuild N ] x11-libs/pango-1.0.4-r1 [ebuild N ] dev-libs/atk-1.0.3-r1 [ebuild U ] x11-libs/gtk+-2.0.6-r2 ---schnapp--- maybe updating x11-libs/gtk+-2.0.6-r2 first would solve the compile problem of pango? How to tell emerge changing it's update order? BTW: The errormessage when compiling pango tells about "parse error" and "gtkliststore.lo" could't be created. This looks more like a broken makefile, doesn't it? next I try is a fresh `update rsync`, maybe that helps. If not, I will upate x11-libs/gtk+-2.0.6-r2 first and then do a `emerge -u world` and tell the results.
No, gtk+2 needs pango and atk to build. What i read in your output snippet, you try to compile gtk+2 but it fails on pango and atk. My guess is that theyre still compiled witht the old gcc. So remove pango and atk, rebuild them and then try to emerge gtk+2.
let me restate my situation, because you didn't get it: - I have a machine running gentoo 1.2 with old gcc -> the aim is to update to gentoo 1.4 with new gcc - but, the description how to do that, is: - first do a `emerge update world` - I executed `emerge update system` succesfully ( old gcc ) - executing `emerge update world` fails, because pango ( not installed, yet ) won't compile. ...so, it is still the old gcc, which is not updated by `emerge update system` nor by `emerge update world` compiling all the things. using the new gcc is far, far away :) ...and, there is no pango nor atk to remove from the system, because both are _not_ isntalled. ! this is the situation, blocking my machine to update from 1.2 to 1.4 ! ! note, I restore the system from backup before any new attempt, so each trial has the same environment ! What I am currently trying is this: I have succesfully(surprisingly) emerged pango and atk, let's see, if `update world` finishes, now, which does not touch pango and atk anymore. I wonder why I could emerge them, but `update world` can't.
Well, if this is the update list with your _old_ gcc you havent updated anything in months ? And i don't see what use it is updating world witht the old gcc. You should update system with the old gcc maybe, then upgrade to a new profile.. bootstrap and then update system with the new gcc. After that comes a full update world for the new gcc. But then i'm no update expert. Makes this hardly a gnome bug (?), but more some update failure. Use the official update guide please, http://www.gentoo.org/doc/upgrade-to-gentoo-1.4.html . Code Listing 2.1 suggests an 'emerge -u world', in normal situations this shouldnt be more than a few packages (if you rsync regulary). I suggest you just move on and focus on getting your base system to gcc3 and then try to upgrade world.
Oh and the first output snippet you gave is _not_ pango failing, it is gtk+2 failing.
`emerge pango` `emerge atk` `emerge -u world` works! dunno the reason for failing `emerge -u world` without having installed pango/atk. the pretend list does say [ebuild N ] x11-libs/pango-1.0.4-r1 [ebuild N ] dev-libs/atk-1.0.3-r1 [ebuild U ] x11-libs/gtk+-2.0.6-r2 which reflects what I have prepared by hand. on the other hand, you are right, I haven't updated the machine for weeks, because there was no need for it (running it's jobs stable, being offline). I am no update specialist, neither. and I haven't tried `update system` nor `update world` before. but as the update guide says, it is adviseable to start with, which "Will probably save you a lot of time and hassle." and you should do it at a later update process, too, which "Rebuilds everything with the gcc-3.2 optimizations you specified." and that is the main reason for upgrading from gentoo 1.2 to 1.4. I don't think that this bug is resolved, I leave it to your hands. IMHO there must be a mistake somewhere in the `update world` procedure - but I don't know if you guys are really interested in fixing it, if I am the only one who has it. for me, this case is closed. thank you very much in helping me. regards, Sascha
Well, even if update world isn't ok, it isn't a gnome problem. An update like this often has its glitches, but i'm glad it worked out in the end. closing this one.