Date: Tue, 20 Mar 2018 09:57:21 -0500 From: Bob Willcox <bob@immure.com> To: Kubilay Kocak <koobs@FreeBSD.org> Cc: freebsd-ports@freebsd.org Subject: Re: What is the status of the ical calendar program? Message-ID: <20180320145721.GA60302@rancor.immure.com> In-Reply-To: <b7b54d55-8b59-09bd-d2c3-c5328b8cefb2@FreeBSD.org> References: <20180320123916.GB56808@rancor.immure.com> <b7b54d55-8b59-09bd-d2c3-c5328b8cefb2@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 20, 2018 at 11:50:44PM +1100, Kubilay Kocak wrote:
> 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
Fair enough, I was simply checking to see if someone already was asware of
this and maybe had a solution.
So, here are the start of the (3836) warnings:
--- main.o ---
In file included from main.C:57:
./ical_start.gen:1:1: warning: ISO C++11 does not allow conversion from string literal to 'char *' [-Wwritable-strings]
"# Generated automatically from startup.tcl.in by configure.",
^
./ical_start.gen:2:1: warning: ISO C++11 does not allow conversion from string literal to 'char *' [-Wwritable-strings]
"# Copyright (c) 1993 by Sanjay Ghemawat",
^
./ical_start.gen:3:1: warning: ISO C++11 does not allow conversion from string literal to 'char *' [-Wwritable-strings]
"###############################################################################",
^
And here are the first two errors:
In file included from main.C:82:
./bitmaps/left.xbm:5:16: error: constant expression evaluates to 128 which cannot be narrowed to type 'char' [-Wc++11-narrowing]
0x00, 0x00, 0x80, 0x01, 0x40, 0x01, 0x20, 0x01, 0x10, 0x01, 0x08, 0x7f,
^~~~
./bitmaps/left.xbm:5:16: note: insert an explicit cast to silence this issue
0x00, 0x00, 0x80, 0x01, 0x40, 0x01, 0x20, 0x01, 0x10, 0x01, 0x08, 0x7f,
^~~~
static_cast<char>( )
./bitmaps/left.xbm:7:28: error: constant expression evaluates to 128 which cannot be narrowed to type 'char' [-Wc++11-narrowing]
0x20, 0x01, 0x40, 0x01, 0x80, 0x01, 0x00, 0x00};
^~~~
./bitmaps/left.xbm:7:28: note: insert an explicit cast to silence this issue
0x20, 0x01, 0x40, 0x01, 0x80, 0x01, 0x00, 0x00};
^~~~
static_cast<char>( )
Finally, the last few errors:
In file included from main.C:85:
./bitmaps/done.xbm:4:16: error: constant expression evaluates to 255 which cannot be narrowed to type 'char' [-Wc++11-narrowing]
0x00, 0x00, 0xff, 0x8f, 0xff, 0x67, 0x03, 0x30, 0x03, 0x18, 0x03, 0x4c,
^~~~
./bitmaps/done.xbm:4:16: note: insert an explicit cast to silence this issue
0x00, 0x00, 0xff, 0x8f, 0xff, 0x67, 0x03, 0x30, 0x03, 0x18, 0x03, 0x4c,
^~~~
static_cast<char>( )
./bitmaps/done.xbm:4:22: error: constant expression evaluates to 143 which cannot be narrowed to type 'char' [-Wc++11-narrowing]
0x00, 0x00, 0xff, 0x8f, 0xff, 0x67, 0x03, 0x30, 0x03, 0x18, 0x03, 0x4c,
^~~~
./bitmaps/done.xbm:4:22: note: insert an explicit cast to silence this issue
0x00, 0x00, 0xff, 0x8f, 0xff, 0x67, 0x03, 0x30, 0x03, 0x18, 0x03, 0x4c,
^~~~
static_cast<char>( )
./bitmaps/done.xbm:4:28: error: constant expression evaluates to 255 which cannot be narrowed to type 'char' [-Wc++11-narrowing]
0x00, 0x00, 0xff, 0x8f, 0xff, 0x67, 0x03, 0x30, 0x03, 0x18, 0x03, 0x4c,
^~~~
./bitmaps/done.xbm:4:28: note: insert an explicit cast to silence this issue
0x00, 0x00, 0xff, 0x8f, 0xff, 0x67, 0x03, 0x30, 0x03, 0x18, 0x03, 0x4c,
^~~~
static_cast<char>( )
So, perhaps the errors could be silenced by inserting casts at the appropriate
places in the generated files.
I will go ahead and open a Bugzilla issue for this. Note that the make output
is 13061 lines long!
Thanks,
Bob
--
Bob Willcox | The amount of flak received on any subject is inversely
bob@immure.com | proportional to the subject's true value.
Austin, TX |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180320145721.GA60302>