Bug 135093 - dev-util/kdevelop-3.3.2 stable request
|
Bug#:
135093
|
Product: Gentoo Linux
|
Version: 2006.0
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: kde@gentoo.org
|
Reported By: StormByte@gmail.com
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: dev-util/kdevelop-3.3.2 stable request
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2006-05-31 18:58 0000
|
Can't compile kdevelop with USE="java php sql -ada -arts -clearcase -debug
-fortran -haskell -pascal -perforce -perl -python -ruby -subversion -xinerama"
(as seen in emerge -pv kdevelop
this is the error message:
/bin/sh ../../libtool --silent --tag=CXX --mode=compile x86_64-pc-linux-gnu-g++
-DHAVE_CONFIG_H -I. -I. -I../.. -I../../lib/interfaces
-I../../lib/interfaces/extensions -I../../lib/util -I/usr/kde/3.5/include
-I/usr/qt/3/include -I. -I/usr/kde/3.5/include -DQT_THREAD_SUPPORT
-D_REENTRANT -Wnon-virtual-dtor -Wno-long-long -Wundef -ansi
-D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts
-Wall -W -Wpointer-arith -Wwrite-strings -DNDEBUG -DNO_DEBUG -O2 -march=k8 -O3
-pipe -fforce-addr -fomit-frame-pointer -funroll-loops -falign-functions=4
-maccumulate-outgoing-args -Wformat-security -Wmissing-format-attribute
-fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE
-DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -c -o
toolsconfigwidgetbase.lo toolsconfigwidgetbase.cpp
addtooldlg.cpp:28:33: kdevapplicationtree.h: No such file or directory
make[3]: *** [addtooldlg.lo] Error 1
make[3]: *** Se espera a que terminen otras tareas....
make[3]: Leaving directory
`/var/tmp/portage/kdevelop-3.2.1-r1/work/kdevelop-3.2.1/parts/tools'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/var/tmp/portage/kdevelop-3.2.1-r1/work/kdevelop-3.2.1/parts'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/var/tmp/portage/kdevelop-3.2.1-r1/work/kdevelop-3.2.1'
make: *** [all] Error 2
!!! ERROR: dev-util/kdevelop-3.2.1-r1 failed.
Call stack:
ebuild.sh, line 1531: Called dyn_compile
ebuild.sh, line 931: Called src_compile
kdevelop-3.2.1-r1.ebuild, line 56: Called kde_src_compile
kde.eclass, line 144: Called kde_src_compile 'all'
kde.eclass, line 279: Called kde_src_compile 'myconf' 'configure' 'make'
kde.eclass, line 275: Called die
!!! died running emake, kde_src_compile:make
!!! If you need support, post the topmost build error, and the call stack if
relevant.
And this is emerge --info:
Portage 2.1_rc3-r3 (default-linux/amd64/2006.0, gcc-3.4.5, glibc-2.3.6-r3,
2.6.16-gentoo-r7 x86_64)
=================================================================
System uname: 2.6.16-gentoo-r7 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor
3800+
Gentoo Base System version 1.6.14
ccache version 2.3 [enabled]
dev-lang/python: 2.4.2
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache: 2.3
dev-util/confcache: 0.4.2-r1
sys-apps/sandbox: 1.2.17
sys-devel/autoconf: 2.13, 2.59-r7
sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils: 2.16.1-r2
sys-devel/libtool: 1.5.22
virtual/os-headers: 2.6.11-r2
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=k8 -O3 -pipe -fforce-addr -fomit-frame-pointer -funroll-loops
-falign-functions=4 -maccumulate-outgoing-args"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config
/usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=k8 -O3 -pipe -fforce-addr -fomit-frame-pointer -funroll-loops
-falign-functions=4 -maccumulate-outgoing-args"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig ccache confcache distlocks metadata-transfer sandbox
sfperms strict"
GENTOO_MIRRORS="http://linuv.uv.es/mirror/gentoo/"
LANG="es_ES.UTF-8"
LC_ALL="es_ES.UTF-8"
LINGUAS="es"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress
--force --whole-file --delete --delete-after --stats --timeout=180
--exclude='/distfiles' --exclude='/local' --exclude='/packages'"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="amd64 X acpi alsa avi bash-completion berkdb bitmap-fonts cairo cjk cli
crypt cups dri eds emboss encode foomaticdb fortran gif glitz gpm gstreamer gtk
gtk2 hal iconv imlib ipv6 isdnlog jpeg kde lzw lzw-tiff mp3 mpeg ncurses nls
nptl opengl pam pcre pdflib perl png pppd python qt quicktime readline
reflection sdl session spell spl ssl tcpd tiff truetype-fonts type1-fonts
unicode usb xorg xpm xv zlib elibc_glibc input_devices_keyboard
input_devices_mouse kernel_linux linguas_es userland_GNU video_cards_nv
video_cards_nvidia video_cards_vesa"
Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS,
PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
Thanks.
Please arches mark kdevelop 3.3.2 stable as that's was supposed to go stable
together with KDE 3.5, too.
It's also needed because as you can see kdevelop 3.2 does not build with Qt
3.3.5 and later (3.3.6-r1 stable).
well I'm having a segfault with r++, I won't be able to give a debug of it til
tomorrow. Everything else within the kdevelop suite works though.
Please advise, and I'll try and have the debug if needed tomorrow night for
you.
r++ segfaults on SPARC too, however I'm not sure what it actually does or how
it should be invoked so that might be part of it.
So anyone care to mention what it is that r++ does?
I'd like to, if I had a clue about it >_> okay okay now i'll take a look to
that.
I think it is their C++ parser for code completion etc. I found a few links
discussing it, but nothing describing it directly. I have been using kdevelop
3.3 for quite some time on amd64 without any issues, as have colleagues. I am
not sure that r++ is supposed to be called directly, and I am unable to find
any major bugs with kdevelop that make it worse than the current stable.
I am open to opinions, but I am of the opinion that it is ready to go stable. I
also agree that no program should just segfault but it does not seem to be
causing breakage here.
Arch teams, your current stable is *broken*. I don't give a damn about r++
segfaulting, no feature seems crippled by that and the command is not supposed
to be ran by users, so _please_ mark this stable to fix your stable tree if you
think well of your users.
x86 is stable now. /me pokes flameeyes to be nice :-P. I care about the users
when I have time to think about them *wink*.
*whistle* >X_X<
What about the first post. Same problem here. have you seen #133537?
stable on ppc. We are the last arch.