On Mon, Oct 4, 2021 at 6:35 AM Mikhail <mp39...@gmail.com> wrote:
>
> On Thu, Sep 16, 2021 at 12:18:36PM +0300, Mikhail wrote:
> > On Wed, Sep 15, 2021 at 11:48:18PM -0400, Daniel Dickman wrote:
> > > On Tue, Sep 14, 2021 at 6:39 AM Mikhail <mp39...@gmail.com> wrote:
> > > >
> > > > On Mon, Sep 13, 2021 at 09:34:54PM +0300, Mikhail wrote:
> > > > > Hello, this is update for net/epic4 port from 2.10.5 to 2.10.10.
> > > > >
> > > > > patch-include_irc_h and patch-source_irc_c were incorporated upstream
> > > > > and should be rm'ed
> > > > >
> > > >
> > > > On IRC I was advised to remove REVISION, new patch is inline.
> > > >
> > > > The maintainer has been contacted, seem he ignores the updates.
> > >
> > > sometimes people take vacations or life comes up. I'd say wait at
> > > least a week or two to see if they will reply.
> > >
> > > If no reply in a week or two, they could be removed.
> >
> > He was contacted in 2019, he replied in 2020 and the reply was that he
> > would update the port, but he never did.
> >
> > Today the mail server reports that there is no such email address.
> >
> > New patch with MAINTAINER removed.
>
> ping
>
I looked at doing this update again, but reading INSTALL it says the following:
You must not try to compile epic with "gcc -O2" because -O2 will
generate bad code that leads to random crashes. When you use -O2,
gcc assumes the source is conformant to ISO C99's requirements about
alias-safety, and EPIC, being a C90 program, does not conform, so the
result is undefined behavior (which means it crashes randomly.) This
is not a bug in EPIC. You must only compile epic with -O.
The current port *does* build with -O2 although the warning seems a
bit... concerning? Doing the update may be no worse than the current
situation. Still, it might be good to verify if the comment is stale
and -O2 is ok, or whether we should switch to using -O.
Also looking at WANTLIB following the update, is pthread still needed?
For now, I've dropped MAINTAINER as we haven't heard from them in a few months.
