If you look at the fcron-2.0.0-r2 ebuild you will see that nano is given as the editor to the configure. But on my system nano is no longer installed, because of the new virtual/editor and i'm a vim fan :) I think nano should not be given "hard" to any ebuild any more. Reproducible: Always Steps to Reproduce: 1. 'emerge -C nano' 2. 'emerge fcron' 3. Actual Results: [...] checking sendmail... /usr/sbin/sendmail checking for sh... /bin/sh checking editor... configure: error: File /usr/bin/nano is not an executable file !!! ERROR: sys-apps/fcron-2.0.0-r2 failed. !!! Function src_compile, Line 38, Exitcode 1 !!! bad ./configure Expected Results: The ebuild should search for an editor, or use the automatic editor detection of configure if this is possible. The easiest workaround is to replace nano in the ebuild with one of your installed editors.
good call.
Another problem is if you set EDITOR="/usr/bin/emacs -nw" that is reasonable as you don;t want to see emacs in a separate X11 window by default in every slow remote connection. However, fcron ebuild fails to recognize such editor complaining that "File /usr/bin/emacs -nw is not an executable file" I've just bumped to that problem when I've been updating to fcron-2.0.0-r3
This bug has regressed in fcron 2.0.1 ... checking sendmail... /usr/sbin/sendmail checking for sh... /bin/sh checking editor... configure: error: File /bin/nano is not an executable file !!! ERROR: sys-apps/fcron-2.0.1 failed. !!! Function econf, Line 449, Exitcode 1 !!! econf failed !!! If you need support, post the topmost build error, NOT this status message.
