From: Ingo Schwarze <schwarze@usta.de>
To: Wynn Wolf Arbor <wolf@oriole.systems>
Cc: discuss@mandoc.bsd.lv
Subject: Re: Compilation with GCC 10 and -fno-common fails for 1.14.5
Date: Thu, 11 Jun 2020 14:02:58 +0200 [thread overview]
Message-ID: <20200611120258.GB65010@athene.usta.de> (raw)
In-Reply-To: <20200611093341.h76sla3ucgcmtd4w@nabokov.fritz.box>
Hi Wolf,
Wynn Wolf Arbor wrote on Thu, Jun 11, 2020 at 11:33:41AM +0200:
> When multiple unneeded (ie HAVE_* is set) compatibility files are
> included in a compiler invocation, the dummy declarations 'int dummy'
> clash with one another.
I'll consider that separately.
> I tried checking whether the development branch has this fixed already,
> but it seems that the CVS web interface [1] is down at the moment (500
> Internal Server Error).
> [1] https://cvsweb.bsd.lv/mandoc/
I just repaired that.
> I also sadly couldn't check out the CVS:
> cvs [checkout aborted]: end of file from server
> (consult above messages if any)
And i repaired that, too.
Thanks for the reports!
Ingo
P.S. @kristaps:
I suspect both got broken by the recent operating system upgrade to
OpenBSD 6.7, which changed the ABI for syscalls between libc and
kernel. So the pre-upgrade programs no longer ran on the new kernel.
Now, both the anoncvs and cvsweb chroot contain up-to-date binaries
again.
--
To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
prev parent reply other threads:[~2020-06-11 12:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 9:33 Wynn Wolf Arbor
2020-06-11 12:02 ` Ingo Schwarze [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200611120258.GB65010@athene.usta.de \
--to=schwarze@usta.de \
--cc=discuss@mandoc.bsd.lv \
--cc=wolf@oriole.systems \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).