37952 – KDE 3.2.0 beta 2 doesn't emerge with autoconf 2.57

Bug 37952 - KDE 3.2.0 beta 2 doesn't emerge with autoconf 2.57

Summary: KDE 3.2.0 beta 2 doesn't emerge with autoconf 2.57

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] KDE (show other bugs)
Hardware:	x86 Linux

Importance:	High blocker (vote)
Assignee:	Gentoo KDE team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2004-01-12 02:50 UTC by Rene Gass
Modified:	2004-01-18 08:08 UTC (History)
CC List:	0 users

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Rene Gass 2004-01-12 02:50:10 UTC

On a fresh Gentoo 1.4 installation, I tried to emerge KDE 3.2.0 beta 2. When making aRts, it died with some aclocal error (sorry, I don't have the exact error message). I emerged KDE 3.1.4 instead, which required a newer version of autoconf (2.57a or 2.58). Now, with autoconf 2.58, I was able to compile KDE 3.2 beta 2. So it seems, the following from kdelibs-3.1.4.ebuild is needed for KDE 3.2 as well:

# kdelibs-3.1.4 requires autoconf-2.57a or better, so we require 2.58
# since that's marked stable.  See
# http://forums.gentoo.org/viewtopic.php?t=122430
# (10 Jan 2004 agriffis)
DEPEND=">=sys-devel/autoconf-2.58


Reproducible: Always
Steps to Reproduce:
1. unblock KDE 3.2 components in /usr/portage/profiles/package.mask
2. emerge kde
Actual Results:  
Error message from autoconf while emerging aRts.

Expected Results:  
Compilation of aRts.

Comment 1 Caleb Tennis (RETIRED) gentoo-dev

2004-01-18 08:08:08 UTC

fixed in portage