From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: mdocml build fails at configure
Date: Wed, 05 Feb 2020 15:18:40 +0100 [thread overview]
Message-ID: <20200205141840.IHpViJWlWo2CAa2hojnqR8R711pVV8rttCWw3kwQhjM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18816@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 697 bytes --]
New comment by ischwarze on void-packages repository
https://github.com/void-linux/void-packages/issues/18816#issuecomment-582428851
Comment:
I think adding that printf/env/make line to automatically detect the default compiler that make(1) uses on the system was a bad idea, i tried to be too clever when writing that. It's not the first time that line is causing portability issues.
I think for the next mandoc release, i'll simply set CC=cc by default - after all, POSIX specifies cc(1) - and ask people who want to use a particular compiler to set CC in configure.local. Besides, most ANSI C compilers ought to work anyway, so finding the best one shouldn't even be all that important.
next prev parent reply other threads:[~2020-02-05 14:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 21:27 [ISSUE] " voidlinux-github
2020-02-04 22:39 ` voidlinux-github
2020-02-04 22:59 ` voidlinux-github
2020-02-05 2:25 ` voidlinux-github
2020-02-05 3:14 ` voidlinux-github
2020-02-05 3:14 ` voidlinux-github
2020-02-05 14:18 ` voidlinux-github [this message]
2020-02-05 14:23 ` voidlinux-github
2020-02-05 16:13 ` voidlinux-github
2020-03-23 17:09 ` [ISSUE] [CLOSED] " leahneukirchen
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=20200205141840.IHpViJWlWo2CAa2hojnqR8R711pVV8rttCWw3kwQhjM@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/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).