As in the summary - kdevelop 3.1.0 builds successfully on amd64. I have built it twice with no problems, and used it for several hours with no crashes. Examining the ebuild it applies a patch specifically for amd64 also. I am using gcc 3.4.1. The ebuild is keyworded -amd64. I suggest changing this to ~amd64, I can't find any current bugs suggesting it will not build. I am using KDE 3.3 also.
Did you see bug #60062?
Yes - it didn't seem appropriate to add it on to that bug. May be I was wrong? This seemed to be a different issue with a different version of the ebuild. Sorry - I should have probably pointed that bug out too.
3.1.0 needs a patch on amd64 first; same patch as 3.1.0_rc2. *** This bug has been marked as a duplicate of 60062 ***
I'm not sure how you got the kdevelop ebuild to build, but I'm getting a consistent build failure on amd64, at what appears to be included inline asm... I don't think this bug should be marked resolved. Here's my build output: make all-recursive make[1]: Entering directory `/var/tmp/portage/kdevelop-3.1.0/work/kdevelop-3.1.0' Making all in bdb make[2]: Entering directory `/var/tmp/portage/kdevelop-3.1.0/work/kdevelop-3.1.0/bdb' Making all in build_unix make[3]: Entering directory `/var/tmp/portage/kdevelop-3.1.0/work/kdevelop-3.1.0/bdb/build_unix' gcc -c -I. -I../.././bdb/dist/../include -D_REENTRANT -D_GNU_SOURCE -ansi -W -Wall -Wchar-subscripts -Wshadow -Wpointer-arith -Wmissing-prototypes -Wwrite-strings -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -DNDEBUG -O2 -O2 -Wformat-security -Wmissing-format-attribute -fPIC ../.././bdb/dist/../mutex/mut_tas.c gcc -c -I. -I../.././bdb/dist/../include -D_REENTRANT -D_GNU_SOURCE -ansi -W -Wall -Wchar-subscripts -Wshadow -Wpointer-arith -Wmissing-prototypes -Wwrite-strings -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -DNDEBUG -O2 -O2 -Wformat-security -Wmissing-format-attribute -fPIC ../.././bdb/dist/../btree/bt_compare.c ../../bdb/mutex/mut_tas.c: In function `__db_tas_mutex_lock': ../../bdb/mutex/mut_tas.c:108: error: `asm' undeclared (first use in this function) ../../bdb/mutex/mut_tas.c:108: error: (Each undeclared identifier is reported only once ../../bdb/mutex/mut_tas.c:108: error: for each function it appears in.) ../../bdb/mutex/mut_tas.c:108: error: syntax error before "volatile" ../../bdb/mutex/mut_tas.c:108: warning: unused variable `__l' make[3]: *** [mut_tas.o] Error 1 make[3]: *** Waiting for unfinished jobs.... make[3]: Leaving directory `/var/tmp/portage/kdevelop-3.1.0/work/kdevelop-3.1.0/bdb/build_unix' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/kdevelop-3.1.0/work/kdevelop-3.1.0/bdb' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/kdevelop-3.1.0/work/kdevelop-3.1.0' make: *** [all] Error 2 !!! ERROR: dev-util/kdevelop-3.1.0 failed. !!! Function kde_src_compile, Line 131, Exitcode 2 !!! died running emake, kde_src_compile:make ==================== infiltrator ~ # emerge info Portage 2.0.50-r10 (default-amd64-2004.2, gcc-3.3.4, glibc-2.3.4.20040808-r0, 2.6.7-gentoo-r14) ================================================================= System uname: 2.6.7-gentoo-r14 x86_64 AMD Athlon(tm) 64 Processor 3200+ Gentoo Base System version 1.5.3 Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CFLAGS="-O2" CHOST="x86_64-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3.3/share/config:/usr/kde/3.3/env:/usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/init.d /etc/terminfo /etc/env.d" CXXFLAGS="-O2" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache" GENTOO_MIRRORS="ftp://sunsite.ualberta.ca/pub/unix/Linux/gentoo/ ftp://ibiblio.org/pub/Linux/distributions/gentoo/ http://ftp-mirror.internap.com/pub/gentoo/ ftp://ftp-mirror.internap.com/pub/gentoo/ http://mirror.datapipe.net/gentoo ftp://ftp.heanet.ie/pub/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X alsa amd64 apm arts avi berkdb bonobo cdr crypt cups dvd encode foomaticdb gdbm gif gnome gpm gtk gtk2 gtkhtml guile imlib java jpeg kde ldap libg++ libwww mikmod motif mozilla mpeg multilib ncurses nls nogcj oggvorbis opengl oss pam pdflib perl png postgres python qt quicktime readline sdl slang spell ssl tcpd truetype xml2 xmms xv zlib"
I honestly didn't do anything to it - I was surprised when it was keyworded -amd64 as it built first time after an emerge sync one day. All I did was edit the ebuilds KEYWORDS, and change -amd64 to ~amd64. Then just emerged. The ebuild already has the following three lines in it, if use amd64; then epatch ${FILESDIR}/${P/.0/_beta1}-bdb-fPIC.patch fi Which is why I thought it had already been patched, that line has been there since I filed this bug. I also thought you should always file new bugs for problems with new versions of software. I can see how this bug can be seen as a duplicate though. I wanted to double check anyway so I did an 'rm -rf /var/tmp/portage', and then reemerged kdevelop-3.1.0. I got this line near to the start, * Applying kdevelop-3.1_beta1-bdb-fPIC.patch... [ ok ] Now my emerge dies in the same way as yours does, and I have no clue why it used to work. I just thought if I deleted any temp files before trying again it would eliminate the possibility of it being my system. I still have kdeveop-3.1.0 installed though, and am using it quite happily. For completeness here is my emerge info, haven't changed anything. Built it 3 times, and then removed /var/tmp/portage and now it dies with the same lines as in above comment. amd64 ~ # emerge info Portage 2.0.50-r10 (gcc34-2004.2, gcc-3.4.1, glibc-2.3.4.20040619-r1, 2.6.8-x86_64) ================================================================= System uname: 2.6.8-x86_64 x86_64 AMD Athlon(tm) 64 Processor 3200+ Gentoo Base System version 1.4.16 ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CFLAGS="-march=k8 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3.3/share/config:/usr/kde/3.3/env:/usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=k8 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs buildpkg ccache" GENTOO_MIRRORS="http://gentoo.osuosl.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X aalib acl acpi afs aim alsa amd64 apache2 apm arts audiofile avi berkdb bonobo cdr crypt cscope cups curl directfb divx4linux dvd dvdr encode esd ethereal evo f77 fam fbcon fftw flac flash foomaticdb gb gd gdbm gif gimpprint ginac gmp gphoto2 gpm gstreamer gtk gtk2 gtkhtml guile icq imagemagick imlib innodb ipv6 jabberjava jikes joystick jpeg kde lcms ldap libg++ libwww linguas_en_GB mad mcal mikmod motif mozilla mpeg mpi msn multilib mysql nas ncurses netcdf nls odbc offensive oggvorbis opengl oscar oss pam pdflib perl plotutils png postgres ppds python qt quicktime readline samba sasl scanner sdl slang slp spell sqlite ssl tcltk tcpd tetex tiff truetype usb vhosts videos wmf wxwindows xinerama xml2 xmms xv xvid yahoo zlib"
After emerge sync, rm -rf /var/tmp/portage again kdevelop now applies both patches cleanly and compiles. I don't have a clue how or why it compiled cleanly for me before, but thanks for fixing it anyway :)
Okay, after the final comment, I can confirm that by deleting /var/tmp/portage and doing a sync, kdevelop 3.1.0 applies *two* patches, and builds without much complaint. It would appear that the emerge system isn't cleaning up after itself, leaving orphaned trees in the work dir? Perhaps a bug should be filed against it? Dunno. Thanks for the updates to the patchlist. Kdevelop *does* build on amd64.
amd64 team: is it possible to mark kdevelop-3.1.x stable now that this issue is solved? --> see bug 74974
no, 3.1.x also seems to be crashing :(
3.1.2 is marked testing
