Portage 2.1 (default-linux/x86/2006.0, gcc-4.1.1, glibc-2.4-r3, 2.6.16-gentoo-r9 i686) ================================================================= System uname: 2.6.16-gentoo-r9 i686 Pentium III (Coppermine) Gentoo Base System version 1.6.14 dev-lang/python: 2.4.2 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 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-r2 sys-devel/gcc-config: 1.3.13-r2 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r5 >>> Compiling source in /usr/src/gentoo/portage/fcron-2.0.2/work/fcron-2.0.2 ... ./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --with-username=cron --with-groupname=cron --with-piddir=/var/run --with-etcdir=/etc/fcron --with-spooldir=/var/spool/cron --with-sendmail=/usr/sbin/sendmail --with-editor=vi --with-cflags=-march=pentium3 -O2 -fomit-frame-pointer -pipe --build=i686-pc-linux-gnu <snip> checking editor... configure: error: File vi is not an executable file !!! Please attach the following file when filing a report to bugs.gentoo.org: !!! /usr/src/gentoo/portage/fcron-2.0.2/work/fcron-2.0.2/config.log !!! ERROR: sys-process/fcron-2.0.2 failed. Call stack: ebuild.sh, line 1539: Called dyn_compile ebuild.sh, line 939: Called src_compile fcron-2.0.2.ebuild, line 52: Called econf '--with-username=cron' '--with-groupname=cron' '--with-piddir=/var/run' '--with-etcdir=/etc/fcron' '--with-spooldir=/var/spool/cron' '--with-sendmail=/usr/sbin/sendmail' '--with-editor=vi' '--with-cflags=-march=pentium3 -O2 -fomit-frame-pointer -pipe' ebuild.sh, line 541: Called die !!! econf failed !!! If you need support, post the topmost build error, and the call stack if relevant. Although my /etc/rc.conf is EDITOR="/usr/bin/vim", why isn't it set to --with-editor=/usr/bin/vim? If it acts as './configure --with-editor=/usr/bin/vim' manually, this error will not come out.
what does env | grep EDITOR give you? the ebuild is supposed to take your EDITOR variable - don't know why it didn't work for you - but lets try to find out ;)
> what does > > env | grep EDITOR > > give you? env | grep EDITOR is EDITOR=/usr/bin/vim It defines as /etc/profile and /etc/rc.conf Tried: env EDITOR=/usr/bin/vim emerge fcron -> fail env EDITOR=/bin/nano emerge fcron -> fail alias vi=/usr/bin/vim && emerge fcron -> fail emerge -C vim && env-update && env EDITOR=/bin/nano emerge fcron -> fail It is --with-editor=vi for specifying EDITOR=/bin/nano why? Why goes in search of vi which does not already exist?
Please merge. *** /usr/portage/sys-process/fcron/fcron-2.0.2.ebuild Wed Mar 16 20:05:56 2005 --- /usr/local/portage/sys-process/fcron/fcron-2.0.2.ebuild Wed Jun 20 20:09:20 2006 *************** *** 55,61 **** --with-etcdir=/etc/fcron \ --with-spooldir=/var/spool/cron \ --with-sendmail=/usr/sbin/sendmail \ ! --with-editor="${EDITOR}" \ --with-cflags="${CFLAGS}" \ || die "bad ./configure" --- 55,61 ---- --with-etcdir=/etc/fcron \ --with-spooldir=/var/spool/cron \ --with-sendmail=/usr/sbin/sendmail \ ! --with-editor="$(which ${EDITOR} 2>/dev/null)" \ --with-cflags="${CFLAGS}" \ || die "bad ./configure" or *** /usr/portage/sys-process/fcron/fcron-2.0.2.ebuild Wed Mar 16 20:05:56 2005 --- /usr/local/portage/sys-process/fcron/fcron-2.0.2.ebuild Wed Jun 20 20:21:09 2006 *************** *** 25,32 **** # so try to set it to the abs path if it isn't if [[ "${EDITOR}" != */* ]] ; then einfo "Attempting to deduce absolute path of ${EDITOR}" ! EDITOR=$(which ${EDITOR} 2>/dev/null) ! [[ -x "${EDITOR}" ]] || \ die "Please set the EDITOR env variable to the path of a valid executable." fi } --- 25,32 ---- # so try to set it to the abs path if it isn't if [[ "${EDITOR}" != */* ]] ; then einfo "Attempting to deduce absolute path of ${EDITOR}" ! EDITOR_ENV=$(which ${EDITOR} 2>/dev/null) ! [[ -x "${EDITOR_ENV}" ]] || \ die "Please set the EDITOR env variable to the path of a valid executable." fi } *************** *** 55,61 **** --with-etcdir=/etc/fcron \ --with-spooldir=/var/spool/cron \ --with-sendmail=/usr/sbin/sendmail \ ! --with-editor="${EDITOR}" \ --with-cflags="${CFLAGS}" \ || die "bad ./configure" --- 55,61 ---- --with-etcdir=/etc/fcron \ --with-spooldir=/var/spool/cron \ --with-sendmail=/usr/sbin/sendmail \ ! --with-editor="${EDITOR_ENV}" \ --with-cflags="${CFLAGS}" \ || die "bad ./configure"
(In reply to comment #3) I had the same problem during gentoo installation. The reason was that EDITOR environment variable was set to "/usr/bin/gvim -f" (and that file didn't exist). The /etc/profile script, which is sourced after chroot'ing into the new gentoo system, sets this variable only if it was not set previosly. However, is _was_ set, hence /etc/profile didn't change it. The appropriate solution for that Problem will be to change the /etc/profile script (or the algo by which it is created) to set EDITOR correctly. This has to be done by the gentoo developers. As a quick solution one can simply set it manually: export EDITOR="nano" emerge fcron NOTE: during installation, the preferred EDITOR is chosen in the file /etc/rc.conf, However, this editor may not yet be installed at that time. In that case fcron will not emerge correctly, even when EDITOR is set to whatever the user entered in rc.conf. This is probably no problem, since rc.conf is edited by the user _after_ she had sourced /etc/profile.
I've got the same problem. echo $EDITOR poped out /usr/bin/vim, which matches the output from which. I ran across this (along with a few other problems that I've solved) in an emerge -e world. I know it worked previously (since I installed it). The error: >>> Emerging (405 of 438) sys-process/fcron-2.0.2 to / * fcron-2.0.2.src.tar.gz size ;-) ... [ ok ] * fcron-2.0.2.src.tar.gz RMD160 ;-) ... [ ok ] * fcron-2.0.2.src.tar.gz SHA256 ;-) ... [ ok ] * fcron-2.0.2.src.tar.gz MD5 ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking fcron-2.0.2.src.tar.gz ;-) ... [ ok ] * Attempting to deduce absolute path of !!! ERROR: sys-process/fcron-2.0.2 failed. Call stack: ebuild.sh, line 1562: Called dyn_setup ebuild.sh, line 665: Called pkg_setup fcron-2.0.2.ebuild, line 30: Called die !!! Please set the EDITOR env variable to the path of a valid executable. !!! If you need support, post the topmost build error, and the call stack if relevant. My CFLAGS are normal, with the only diffrence being from the standard is -fomit-frame-pointer, which worked when I was compiling it, so I seriously doubt it would be a CFLAG issue here.
Ok. Some good news here - I've got fcron compiling. Diffrence? The new compile is being done under the root account instead of a sudo, so it may be a permission problem steming from sudo. Maybe someone else could comment on this, and make sure it isn't just my set-up that is acting funny?
FIXED in >=3.0.2-r1