Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 107821 - arts-3.5_beta1-r1 fails for autoconf-2.59 says >=autoconf2.13 is needed
Summary: arts-3.5_beta1-r1 fails for autoconf-2.59 says >=autoconf2.13 is needed
Status: VERIFIED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: x86 Linux
: High minor (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-01 14:55 UTC by Sirus
Modified: 2006-01-15 13:00 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sirus 2005-10-01 14:55:17 UTC
I have autoconf-2.59 and no other versions I get this when emerging the kde-3.5 beta

*** YOU'RE USING Autoconf version 2.13.
*** KDE requires autoconf 2.53 or newer
make[1]: *** [cvs] Error 1
make: *** [all] Error 2

Everyone says this will fix it:  "export WANT_AUTOCONF=2.5" it does not. this
does though: "AUTOCONF=/usr/bin/autoconf-2.59; export AUTOCONF"


Reproducible: Always
Steps to Reproduce:
1.ACCEPT_KEYWORDS=~x86 emerge -U kde-3.5*
2.
3.

Actual Results:  
*** YOU'RE USING Autoconf version 2.13.
*** KDE requires autoconf 2.53 or newer
make[1]: *** [cvs] Error 1
make: *** [all] Error 2

Expected Results:  
AUTOCONF=/usr/bin/autoconf-2.59; export AUTOCONF
fixes problem for me
Comment 1 Gregorio Guidi (RETIRED) gentoo-dev 2005-10-02 03:13:46 UTC
Please post your 'emerge info'. 
Comment 2 Sirus 2005-10-02 08:23:42 UTC
Stareater ~ # emerge info
Portage 2.0.51.22-r2 (default-linux/x86/2005.1, gcc-3.3.5-20050130,
glibc-2.3.5-r1, 2.6.13-gentoo i686)
=================================================================
System uname: 2.6.13-gentoo i686 AMD Athlon(tm)
Gentoo Base System version 1.6.13
dev-lang/python:     2.3.5-r2
sys-apps/sandbox:    1.2.11
sys-devel/autoconf:  2.59-r6
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
sys-devel/libtool:   1.5.18-r1
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=athlon-xp -ffast-math -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown
/usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown
/usr/lib/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=athlon-xp -ffast-math -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms"
GENTOO_MIRRORS="ftp://gentoo.chem.wisc.edu/gentoo/
ftp://cudlug.cudenver.edu/pub/mirrors/distributions/gentoo/
ftp://gentoo.llarian.net/pub/gentoo"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 3dnow X aac aim alsa apm arts avi berkdb bitmap-fonts cdr crypt curl
eds emboss encode fam fbcon flac foomaticdb gdbm gif gpm gstreamer imlib jpeg
kde libg++ libwww mad mikmod mmx motif mp3 mpeg mpeg2 mpeg4 ncurses nls ogg
oggvorbis openal opengl oss pam pda pdflib perl png python qt quicktime readline
samba sdl spell sse ssl svga tcltk tcpd tiff truetype truetype-fonts type1-fonts
videos vorbis xine xml2 xmms xv zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY

Stareater ~ #   
Comment 3 Gregorio Guidi (RETIRED) gentoo-dev 2005-10-18 07:54:55 UTC
Is this still happening? It seems no one can reproduce it... 
 
Comment 4 Marcus D. Hanwell (RETIRED) gentoo-dev 2005-11-27 09:15:19 UTC
Not been able to reproduce here either, closing due to lack of response. Please 
reopen if this is still an issue. 
Comment 5 Carsten Lohrke (RETIRED) gentoo-dev 2005-12-25 05:39:16 UTC
No feedback.
Comment 6 Sirus 2006-01-15 13:00:39 UTC
(In reply to comment #5)
> No feedback.
> 
It only happens with kde-3.x today I tried to upgrade to the newest and got the same thing again. I used the same command I posted above to get it to work again. It's probably just my system. I'm sure I fucked something up with portage or something. There are lots and lots of reports on google of people with the same or very similar problems but maybe they just screwed up the same thing that I must have.