From: Wynn Wolf Arbor <email@example.com>
Subject: Compilation with GCC 10 and -fno-common fails for 1.14.5
Date: Thu, 11 Jun 2020 11:33:41 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
GCC 10 has switched from -fcommon to -fno-common as a default, breaking
compilation with the current release of mandoc:
compat_getline.c:5: multiple definition of `dummy';
compat_err.o:mandoc-1.14.5/compat_err.c:5: first defined here
When multiple unneeded (ie HAVE_* is set) compatibility files are
included in a compiler invocation, the dummy declarations 'int dummy'
clash with one another.
Ordinarily I would have sent a patch along, but I am not sure what
solution is preferred here. I can think of the following:
* Simply have a unique name for each dummy declaration per file.
* Make sure that unneeded compatibility files are not included in the
build. This seems a decent albeit more complex and disruptive
I tried checking whether the development branch has this fixed already,
but it seems that the CVS web interface  is down at the moment (500
Internal Server Error). I also sadly couldn't check out the CVS:
cvs [checkout aborted]: end of file from server (consult above messages if any)
There were no previous messages, and I don't know how to make CVS more
I did not find anything through a cursory check of the mandoc-source
mailing list archive, so I'm assuming this issue is still present.
Thanks for your time!
To unsubscribe send an email to email@example.com
next reply other threads:[~2020-06-11 9:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 9:33 Wynn Wolf Arbor [this message]
2020-06-11 12:02 ` Ingo Schwarze
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).