Quoting Michael Nottebrock <[EMAIL PROTECTED]>:
[EMAIL PROTECTED] schrieb:
I'm upgrading kde on 6 machines AMD and all 6 are seeing this.
Making all in kjs
gmake[2]: Entering directory
`/usr/ports/x11/kdelibs3/work/kdelibs-3.5.0/kjs'
cd .. && /bin/sh
/usr/ports/x11/kdelibs3/work/kdelibs-3.5.0/admin/missing --run autoheader
configure.in:24: error: Autoconf version 2.58 or higher is required
aclocal.m4:446: AM_INIT_AUTOMAKE is expanded from...
configure.in:24: the top level
autoheader: autom4te failed with exit status: 1
at /usr/local/bin/autoheader line 163
How come all 6 machines of yours have an unsuffixed autoheader in
/usr/local/bin? Putting the autoconf/automake scripts into PATH has a
fair amount of breakage potential - like tickling obscure bugs in KDE's
buildsystem. :)
I guess you put symlinks into /usr/local/bin that point to the suffixed
auto*-scripts of the auto*-ports - don't do that. KDevelop doesn't
require it anymore and there's the devel/gnu-auto* ports now which
install unpatched versions of the autotools into /usr/local/gnu-autotools.
Michael, you seem to have hit the nail on the head. I just realized
that all the machines have an complete set of auto's in /usr/local/bin,
since first installing the operating system and I didn't realize it. I
had done pkd_delete for all but they didn't get deleted and I didn't
check. I apologize for the noise.
-r-xr-xr-x 1 root wheel 6191 Jul 31 2004 /usr/local/bin/autoconf
-r-xr-xr-x 1 root wheel 6752 Jul 31 2004 /usr/local/bin/autoheader
-r-xr-xr-x 1 root wheel 31250 Jul 31 2004 /usr/local/bin/autom4te
-r-xr-xr-x 1 root wheel 216043 Aug 1 2004 /usr/local/bin/automake
-r-xr-xr-x 1 root wheel 211032 Sep 7 2004 /usr/local/bin/automake18
-r-xr-xr-x 1 root wheel 10895 Jul 31 2004 /usr/local/bin/autoreconf
-r-xr-xr-x 1 root wheel 15025 Jul 31 2004 /usr/local/bin/autoscan
-r-xr-xr-x 1 root wheel 32134 Jul 31 2004 /usr/local/bin/autoupdate
I have erased them all and am in the process of recomiling kdelibs3
that I am sure will work now.
You can add those to your PATH whenever you need them (i.e. when doing
development work, not when compiling ports).
I would like to think that I have followed the instructions in UPDATING
to the letter until the portupgrade -O arts\* kde\* \*kde-i18n\* starts
to fail because of kdelibs. I then went to /usr/ports/x11/kdelibs3 and
tried to just build it unsuccessfully.
BTW, my autoconf is /usr/ports/x11/kdelibs3 # ls -d /var/db/pkg/autoconf*
/var/db/pkg/autoconf-2.59_2
Suggestions appreciated,
I just committed a fix to the kdelibs port that should prevent it from
trying to invoke autoheader. Cvsup/portsnap, do a portsclean -C and then
restart your portupgrade, should work now (even with auto* in PATH).
Thanks a lot Michael. That will hopefully keep anyone else from being
as dumb as I and not checking.
ed
Cheers,
--
,_, | Michael Nottebrock | [EMAIL PROTECTED]
(/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org
\u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org
_______________________________________________
kde-freebsd mailing list
[email protected]
http://freebsd.kde.org/mailman/listinfo/kde-freebsd
