Summary: | vim emerge fail on src_compile() | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | MIKE MacMartin <mike> |
Component: | Current packages | Assignee: | Aron Griffis (RETIRED) <agriffis> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
MIKE MacMartin
2003-07-13 15:39:09 UTC
Hi. Please create an attachment with the full output of "emerge vim-core". I don't have any idea what's going wrong yet. Thanks. As requested, as follows is an output of emerge vim-core. I have tried redownloading the source to the same result. isis root # emerge vim-core Calculating dependencies ...done! >>> emerge (1 of 1) app-editors/vim-core-6.2-r1 to / >>> md5 src_uri ;-) vim-6.2.tar.bz2 >>> md5 src_uri ;-) vim-6.2-lang.tar.gz >>> md5 src_uri ;-) vim-6.2.011-gentoo-patches.tar.bz2 >>> md5 src_uri ;-) vim-6.2.011-patches.tar.bz2 >>> Unpacking source... >>> Unpacking vim-6.2.tar.bz2 to /var/tmp/portage/vim-core-6.2-r1/work >>> Unpacking vim-6.2-lang.tar.gz to /var/tmp/portage/vim-core-6.2-r1/work >>> Unpacking vim-6.2.011-gentoo-patches.tar.bz2 to /var/tmp/portage/vim-core-6.2-r1/work >>> Unpacking vim-6.2.011-patches.tar.bz2 to /var/tmp/portage/vim-core-6.2-r1/work * Filtering vim patches... 6.2.001: runtime/doc/insert.txt runtime/doc/tags src/version.c 6.2.002: src/option.c src/version.c 6.2.003: src/gui_gtk_x11.c src/version.c 6.2.004: src/normal.c src/version.c 6.2.005: src/gui_gtk.c src/version.c 6.2.006: src/main.c src/netbeans.c src/proto/netbeans.pro src/version.c 6.2.007: src/if_cscope.c src/version.c 6.2.008: src/mbyte.c src/version.c 6.2.009: (nsis/gvim.nsi) src/version.c 6.2.010: src/charset.c src/version.c 6.2.011: src/os_unix.c src/version.c * Applying filtered vim patches...... [ ok ] * Applying various patches (bugfixes/updates)... * 001_all_vim-4.2-speed_t.patch.gz... [ ok ] * 002_all_vim-5.1-vimnotvi.patch.gz... [ ok ] * 003_all_vim-5.6a-paths.patch.gz... [ ok ] * 004_all_vim-6.0-fixkeys.patch.gz... [ ok ] * 006_all_vim-6.0r-crv.patch.gz... [ ok ] * 007_all_vim-6.0-gcc31.patch.gz... [ ok ] * Done with patching >>> Source unpacked. make: Entering directory `/var/tmp/portage/vim-core-6.2-r1/work/vim62/src' make: *** No rule to make target `auto/configure'. Stop. make: Leaving directory `/var/tmp/portage/vim-core-6.2-r1/work/vim62/src' !!! ERROR: app-editors/vim-core-6.2-r1 failed. !!! Function src_compile, Line 119, Exitcode 2 !!! make auto/configure failed My first guess is that you have an old version of the vim eclass. Does an "emerge sync" fix anything? an "emerge sync" does not. This may be a problem with the source itself, trying to build something that isn't there. No, it's not a problem with the source. I understand what is happening, just not why it is happening. You don't have an old copy of the eclass in your overlay area, do you? The reason I'm pursuing this angle is because of the following lines in the eclass: # vim-6.2 changed the name of this rule from auto/configure to autoconf confrule=auto/configure grep -q ^autoconf: src/Makefile && confrule=autoconf make -C src $confrule || die "make $confrule failed" These lines work for all the vim-6.2 installations except for yours. For some reason the obselescent "make auto/configure" is being run, which means one of two things: (1) you're getting an old version of the eclass, or (2) there is an error occurring in the lines above that is specific to your machine. Try this: Edit vim.eclass and add at the top of src_compile, "set -x". That will cause bash to spit out the lines that it's running. Then emerge vim-core. If you don't see any differences, then vim-core is getting the eclass from somewhere else on your system. If you do see changes, perhaps they will lead us to the solution. Good call. I don't know where $PORTDIR_OVERLAY/eclass/vim.eclass came from (I looked for ebuilds which weren't in $PORTDIR_OVERLAY, but didn't think of eclasses), but it was an old version that was being picked up. Anyway, the problem is now resolved. Great, closing the bug then |