after emerging fcron and trying to run crontabs I see that crontab fall to infinite loop printing "(setopt) Warning: getopt returned" with a crazy speed. An attempt to run fcron service makes the same in the syslog. No need to mention that both crontab and fcron do not produce any useful outcome. Reproducible: Always Steps to Reproduce: 1. emerge fcron 2. crontab /etc/crontab Actual Results: (setopt) Warning: getopt returned (setopt) Warning: getopt returned (setopt) Warning: getopt returned (setopt) Warning: getopt returned (setopt) Warning: getopt returned (setopt) Warning: getopt returned (setopt) Warning: getopt returned (setopt) Warning: getopt returned (setopt) Warning: getopt returned (setopt) Warning: getopt returned (setopt) Warning: getopt returned Expected Results: It is expected that it just works :) fcron-2.0.0-r3
after investigating this issue further, I paid attention that my fcron emerge log is full of the following warnings: warning: comparison is always false due to limited range of data type with advises on debian mail-lists to use -fsigned-char in CFLAGS against such warnings. The advise helped and fcron, after being recompiled with -fsigned-char now works fine. Please add this flag to all ebuilds of fcron for PPC platform - on x86 fcron works fine without such flag.
I think the bug can be closed with that advise about flags.
