Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 53777 - emerge vim-core-6.2-r7 fails
Summary: emerge vim-core-6.2-r7 fails
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Vim Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-12 23:33 UTC by Anton Koinov
Modified: 2004-06-25 11:32 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 Anton Koinov 2004-06-12 23:33:32 UTC
Emerge of vim-core fails with the following error. It fails the same way on two machines, that are configured quite differently (see emerge info below).

make: Entering directory `/var/tmp/portage/vim-core-6.2-r7/work/vim62/src'
if test ! -f configure.save; then mv configure configure.save; fi
autoconf
autoconf: Undefined macros:
make: *** [autoconf] Error 1
make: Leaving directory `/var/tmp/portage/vim-core-6.2-r7/work/vim62/src'


Reproducible: Always
Steps to Reproduce:




Machine 1:

Portage 2.0.50-r8 (default-x86-2004.0, gcc-3.3.3, glibc-2.3.2-r9, 2.6.5-gentoo-r1)
=================================================================
System uname: 2.6.5-gentoo-r1 i686 AMD Athlon(tm) XP 2100+
Gentoo Base System version 1.4.16
ccache version 2.3 [enabled]
Autoconf: sys-devel/autoconf-2.59-r3
Automake: sys-devel/automake-1.8.3
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-march=athlon-xp -O3 -pipe"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref
/usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/init.d /etc/terminfo /etc/env.d"
CXXFLAGS="-march=athlon-xp -O3 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox userpriv usersandbox"
GENTOO_MIRRORS="http://128.213.5.34/gentoo/ http://mirror.datapipe.net/gentoo
http://mirror.datapipe.net/gentoo http://gentoo.mirrors.pair.com/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="3dnow X alsa apm arts avi berkdb cdr crypt cups encode esd foomaticdb gdbm
gif gnome gphoto2 gpm gtk gtk2 imlib java jpeg kde libg++ libwww mad mikmod mmap
mmx motif mozilla mpeg ncurses nls nptl oggvorbis opengl oss pam pdflib perl png
ppds python qt quicktime readline samba sdl slang spell sse ssl static svga tcpd
tiff truetype usb x86 xml2 xmms xv zlib"


Machine 2:

Portage 2.0.50-r8 (default-x86-2004.0, gcc-3.3.3, glibc-2.3.2-r9, 2.4.26)
=================================================================
System uname: 2.4.26 i686 Pentium Pro
Gentoo Base System version 1.4.16
ccache version 2.3 [enabled]
Autoconf: sys-devel/autoconf-2.59-r3
Automake: sys-devel/automake-1.8.3
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O2 -march=i686 -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3/share/config /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/init.d /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=i686 -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox userpriv usersandbox"
GENTOO_MIRRORS="ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo
ftp://mirrors.tds.net/gentoo ftp://gentoo.ccccom.com http://gentoo.ccccom.com"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X apm arts avi berkdb crypt cups encode foomaticdb gdbm gif gnome gpm gtk
gtk2 imlib jpeg kde libg++ libwww mad mikmod motif mpeg ncurses nls oggvorbis
opengl oss pam pdflib perl png python qt quicktime readline sdl slang spell ssl
svga tcltk tcpd truetype x86 xml2 xmms xv zlib"
Comment 1 Anton Koinov 2004-06-12 23:38:26 UTC
Sorry, entered the bug in the wrong place, trying to move...
Comment 2 Ciaran McCreesh 2004-06-13 06:58:23 UTC
I can't reproduce this using the same autoconf version. Could you please try vim-core 6.3 (you'll need to use vim/gvim 6.3 with this) and see whether the bug still occurs?
Comment 3 Anton Koinov 2004-06-13 12:10:24 UTC
Same thing on both systems running "ACCEPT_KEYWORDS=~x86 e =vim-6.3":

 * Done with patching
>>> Source unpacked.
make: Entering directory `/var/tmp/portage/vim-core-6.3/work/vim63/src'
if test ! -f configure.save; then mv configure configure.save; fi
autoconf
autoconf: Undefined macros:
make: *** [autoconf] Error 1
make: Leaving directory `/var/tmp/portage/vim-core-6.3/work/vim63/src'

!!! ERROR: app-editors/vim-core-6.3 failed.
!!! Function src_compile, Line 193, Exitcode 2
!!! make autoconf failed
Comment 4 Anton Koinov 2004-06-13 12:12:35 UTC
Oops forgot to expand the alias -- just to avoid confision 'e' is an alias for 'emerge -v' on my system.
Comment 5 Anton Koinov 2004-06-13 12:25:34 UTC
There is probably something specific to my setup. Although, the two systems were installed independently from scratch about two months apart and are fairly different configuration-wise (one is a server, the other is a desktop, and as such have quite different sets of packages).

When I installed the first system (the one with 2.4 kernel), I was able to install vim-6.2-r7 (and that is what is currently installed there). I was never able to install vim on the second system (2.6 kernel), any version not even vim-6.2-r7 version. At that time I tried re-emerging vim-6.2-r7 on the 2.4 system, and it failed with the same error -- my conclusion is it is not vim but rather some other package (portage, autoconf, etc.) that is the cause for the problem.

Ket me know how I can help, I do not know autoconf, but guess it is never too late to learn it :)
Comment 6 Ciaran McCreesh 2004-06-16 07:50:13 UTC
Random shot in the dark: what happens if you emerge vim --nodeps? You'll probably need to install all of vim's deps except vim-core first.

Also, I assume you've tried reemerging autoconf?
Comment 7 Anton Koinov 2004-06-16 16:31:47 UTC
yes, tried reemerging autoconf, tried it again now too, same problem (autoconf emerges OK).

The result of emerge vim --nodeps:

 * Done with patching
>>> Source unpacked.
make: Entering directory `/var/tmp/portage/vim-6.2-r8/work/vim62/src'
if test ! -f configure.save; then mv configure configure.save; fi
autoconf
autoconf: Undefined macros:
make: *** [autoconf] Error 1
make: Leaving directory `/var/tmp/portage/vim-6.2-r8/work/vim62/src'

!!! ERROR: app-editors/vim-6.2-r8 failed.
!!! Function src_compile, Line 193, Exitcode 2
!!! make autoconf failed
Comment 8 Aron Griffis (RETIRED) gentoo-dev 2004-06-18 11:47:56 UTC
Anton, looks like we need more output from autoconf to determine what is happening in your setup.  Could you please do the following?

1. mv /usr/bin/autoconf /usr/bin/autoconf.real
2. create a new file /usr/bin/autoconf with the following lines

    #!/bin/bash
    exec $0.real --verbose "$@"

3. chmod +x /usr/bin/autoconf
4. try emerging vim again and see if there is any helpful output.  If the output is long, please create an attachment instead of pasting it inline.

Thanks and sorry for the inconvenience.
Comment 9 Anton Koinov 2004-06-18 19:01:33 UTC
Suggestion did not work because of:

my $binary     = "$0-2.13";
my $binary_new = "$0-2.59";

which made it call autoconf.real-2.13, which does not exist.

But, I was able to install vim. The problem is, it wants autoconf 2.5. Setting "export WANT_AUTOCONF='2.5'" does not work, because something before autoconf resets this environment variable back to 2.1 (the following print statement added to the start of autoconf prints 2.1: print "Autoconf: $ENV{WANT_AUTOCONF}\n";)

I am not able to determine where WANT_AUTOCONF is reset ot 2.1, help appreciated.
Comment 10 Ciaran McCreesh 2004-06-18 19:18:30 UTC
It's set in eclass/vim.eclass:192:

	# autoconf-2.13 needed for this package -- bug 35319
	WANT_AUTOCONF_2_1=yes WANT_AUTOCONF=2.1 \
		make -C src $confrule || die "make $confrule failed"

Looks like we're getting somewhere here...
Comment 11 Anton Koinov 2004-06-18 20:26:37 UTC
OK, so what do we do with this? Autoconf 2.1 definitely doesn't work for me, but works for you, right? Why?

As I mentioned, once I forced autoconf 2.5 by overriding the variable in autoconf, I was able to emerge vim--on my systems it works with 2.5.

Is the bug 35319 obsolete now, maybe vim ebuid should be switched to 2.5.
Comment 12 Ciaran McCreesh 2004-06-21 09:48:36 UTC
I'm trying to get every arch's stable tree up to a recent enough level that I can remove older ebuilds and change this in the eclass.

ppc64: please try to get >=app-editors/vim-core-6.2-r9 stable if possible.
amd64: ditto for >=app-editors/gvim-6.2-r9
Comment 13 Jason Huebel (RETIRED) gentoo-dev 2004-06-22 13:04:47 UTC
6.3 stable on amd64
Comment 14 Ciaran McCreesh 2004-06-25 11:11:26 UTC
vim-6.3 stable on ppc64 now, removing them from the Cc: list and cleaning out old ebuilds...
Comment 15 Ciaran McCreesh 2004-06-25 11:32:45 UTC
The eclass now uses autoconf 2.5 instead of 2.1. Should hopefully be fixed, please reopen if not. Cheers.