Date: Tue, 20 Mar 2018 23:50:44 +1100 From: Kubilay Kocak <koobs@FreeBSD.org> To: Bob Willcox <bob@immure.com> Cc: freebsd-ports@freebsd.org Subject: Re: What is the status of the ical calendar program? Message-ID: <b7b54d55-8b59-09bd-d2c3-c5328b8cefb2@FreeBSD.org> In-Reply-To: <20180320123916.GB56808@rancor.immure.com> References: <20180320123916.GB56808@rancor.immure.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 20/03/2018 11:39 pm, Bob Willcox wrote: > Attempting to build ical on any of my 12.0-CURRENT systems results in this > error: > > fatal error: too many errors emitted, stopping now [-ferror-limit=] > 3836 warnings and 20 errors generated. > *** [main.o] Error code 1 > > make[1]: stopped in /usr/ports/deskutils/ical/work/ical-2.2 > 1 error > > make[1]: stopped in /usr/ports/deskutils/ical/work/ical-2.2 > ===> Compilation failed unexpectedly. > Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to > the maintainer. > *** Error code 1 > > Stop. > make: stopped in /usr/ports/deskutils/ical > > So it looks like ical is currently broken in CURRENT. Are there any plans to > fix this? Alternatively, is there some other calendar program that folks use > that is a good replacement. So far, the several I have tried (xcaledar, > phpicalendar, gsimplecal, & gnome-calendar) don't seem like good substitutes. Hi Bob, The above log doesn't include the reasons why it failed (the error(s) are further up), which will be the first port of call figuring out what's happening. Also note that CURRENT recently introduced Clang 6.0.0, which caused many ports to fail, many of which haven't been fixed yet. This could be one of them. I'd start by opening a Bugzilla issue "deskutils/ical: Fails to build on CURRENT", and include the full build log as an attachment. Please reply here with the Bugzilla ID/url when you do so others can follow and/or assist there. Given the port doesn't currently have a maintainer, I'd then (either myself, or with help from others here, on the mailing lists or on IRC) try to isolate the issue and provide a patch. ./koobs
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b7b54d55-8b59-09bd-d2c3-c5328b8cefb2>