I'm trying to update kde to 3.2.2: > emerge kde When it is bringing in kdebase-3.2.2 it stops with the following: ----- snip ----- checking if konqueror should be compiled... yes checking if kdesktop should be compiled... yes checking if kdm should be compiled... yes configure: creating ./config.status Good - your configure finished. Start make now !!! ERROR: kde-base/kdebase-3.2.2 failed. !!! Function kde_src_compile, Line 129, Exitcode 2 !!! died running emake, kde_src_compile:make --- end --- There are several reported bugs on this issue and I've read them and updated the following (replacing existing installs and in one place downgrading the openmotif from 2.2.2-r1): [ebuild R ] sys-devel/m4-1.4-r1 [ebuild R ] sys-devel/automake-1.8.3 [ebuild R ] sys-devel/autoconf-2.59-r3 [ebuild R ] x11-libs/openmotif-2.1.30-r4 [ebuild R ] net-fs/samba-3.0.2a-r2 but it still halts on kdebase-3.2.2 line 129, with the above quoted error. Reproducible: Always Steps to Reproduce: 1. emerge "=kdebase-3.2.2" 2. wait 2m47s 3. stare at error Actual Results: ooh yes, got the error all right Expected Results: installed kdebase-3.2.2 > emerge info Portage 2.0.50-r8 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r3, 2.4.20-openmosix-r6) ================================================================= System uname: 2.4.20-openmosix-r6 i686 AMD Athlon(tm) MP 2800+ Gentoo Base System version 1.4.3.10 Autoconf: sys-devel/autoconf-2.59-r3 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon -O2 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /opt/tomcat/conf /sbin/functions.sh /sbin/rc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-march=athlon -O2 -pipe -fomit-frame-pointer" DISTDIR="/home/gentoo/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j3" PKGDIR="/home/gentoo/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3ds X aalib acpi acpi4linux alsa apache2 apm arts avi berkdb bindist bonobo cdr cjk clanJavaScript clanVoice crypt cups dedicated dga directfb dnd doc dv dvd dvdr emacs encode esd evms2 fbcon ffmpeg flac foomaticdb gd gdbm geoip ggi gif ginac glut gnome gphoto2 gpm gps gtk gtk2 gtkhtml imap imlib java javascript jbig jdepend joystick jpeg junit kde lcms libg++ libwww mad maildir md5sum mikmod mldonkeypango mng motif mozilla mpeg mpeg4 msn ncurses nls nvidia objc odbc offensive oggvorbis openal opengl openssh oss pam pdflib perl png postgres ppds python qhull qt quicktime readline regexp rogue samba scanner sdl slang slp speex spell sse ssl stencil-buffer svga tcltk tcpd tetex tiff transcode truetype type1 usb videos wmf x86 xatrix xface xinerama xml xml2 xmms xv xvid yahoo zlib zvbi"
Oh, I forgot to mention that I did an emerge sync yesterday (2004 06 15)
what happens if you go into the WORKDIR and try running make by hand?
Created attachment 33822 [details, diff] Patch to fix problems with docbook I think this is the same bug I'm experiencing, though the report given isn't exactly explicit. There's a problem with the path to the docbook. A guy here describes it in more detail: http://tim.suttonfamily.co.uk/modules.php?name=News&file=article&sid=61 I don't claim to have read it fully, but I've whipped up a patch that'll hide the problem until the maintainer fixes it, assuming your KDE directory is /usr/kde/3.2, and you have ksgmltools2, or something. Place the patch in /usr/portage/kde-base/kdebase/files, and add the following line into the src_unpack() section of the kdebase-3.2.2.ebuild: epatch ${FILESDIR}/${P}-docbook.patch Hope that helps, sorry if it doesn't - it's just a dirty hack.
http://dev.gentoo.org/~satai/sgmlfix.html don't think we can do anything here, sounds like something went wrong in an install
