On a 2 day old Gentoo install, Ultra10, the only problem I have come across is that it is impossible for me to emerge "chrony". I can't be much more specific about it, sorry. Reproducible: Always Steps to Reproduce: 1.emerge chrony 2. 3. Actual Results: Calculating dependencies ...done! >>> emerge (1 of 1) net-misc/chrony-1.19 to / >>> md5 src_uri chrony-1.19.tar.gz >>> Unpacking source... >>> Unpacking chrony-1.19.tar.gz to /var/tmp/portage/chrony-1.19/work * Applying chrony-1.19-conf.c-gentoo.diff... [ ok ] * Applying chrony-1.19-chrony.conf.example-gentoo.diff... [ ok ] >>> Source unpacked. Unrecognized option : --host=sparc-unknown-linux-gnu Unrecognized option : --datadir=/usr/share Unrecognized option : --sysconfdir=/etc Unrecognized option : --localstatedir=/var/lib Unrecognized option : --enable-readline Sorry, I don't know how to build this software on your system. !!! ERROR: net-misc/chrony-1.19 failed. !!! Function econf, Line 324, Exitcode 1 !!! econf failed Expected Results: chrony! There is not much to tell, aside the basic install I have emerged: Apache vsftpd ncftp gpm irssi elinks prozilla samba And nothing else I can think of. No X11.
Created attachment 18866 [details, diff] Patch to fix econf problem Hi, econf fails because the configure script coming with chrony is just braindead :) The attached patch fixes this, *but* chrony fails with a gcc parse error during compilation. One reason might be because the author doesnt provide build support for Linux-Sparc[64]. A quick look at the configure script explains it (removed unimportant lines): 17 OPERATINGSYSTEM=`uname -s` 18 VERSION=`uname -r` 19 MACHINE=`uname -m` 20 21 SYSTEM=${OPERATINGSYSTEM}-${MACHINE} (gives "Linux-Sparc64" for $SYSTEM here) 71 case $SYSTEM in 72 SunOS-sun4* ) 93 Linux-i[3456]86 | Linux-ppc* ) 104 BSD/386-i[3456]86 ) 112 NetBSD-* ) 118 SunOS-i86pc* ) 127 CYGWIN32_NT-i[3456]86 ) 133 * ) 134 echo "Sorry, I don't know how to build this software on your system. As you see, "Linux-Sparc64" or "Linux-Sparc" would result in the "Sorry blah blah" error. My patch adds one sed instruction to the ebuild src_unpack which adds a match to Linux-Sparc* but as said above the compilation borks after a while. In short, I'd suggest to remove arch "sparc" from the ebuild and that the submitter contacts the Author of Chrony about a Linux-Sparc version if needed.
I do notice that while the chrony-1.19.99.2.ebuild file complains about all the unrecognized options, it will actually build. So I've marked the chrony-1.19.99.2.ebuild stable and masked the old chrony-1.19.ebuild. Wait at least half an hour before syncing your portage tree again, then emerge chrony again.
Closing as no new problems have been reported.
