From: Kristaps Dzonsons <kristaps@bsd.lv>
To: tech@mdocml.bsd.lv, joerg@britannica.bec.de
Subject: [PATCH] mandoc & pcc
Date: Thu, 24 Feb 2011 12:06:53 +0100 [thread overview]
Message-ID: <4D663BCD.1000804@bsd.lv> (raw)
[-- Attachment #1: Type: text/plain, Size: 306 bytes --]
The following allows mandoc to be compiled with pcc, which didn't work
before because the strlcat/strlcpy test returned bogus results (the -W
flag for flagging missing function prototypes didn't work).
Joerg, can you verify that this works ok with your zany architectures
out there?
Thanks,
Kristaps
[-- Attachment #2: patch.pcc.txt --]
[-- Type: text/plain, Size: 1064 bytes --]
? config.h
? config.log
? foo.1
? mandoc
? patch.eqn.txt
? patch.eqn2.txt
? patch.foo1.txt
? patch.foo2.txt
? patch.ns.txt
? patch.pcc.txt
? patch.txt
? test-foo.c
? regress/output
Index: Makefile
===================================================================
RCS file: /usr/vhosts/mdocml.bsd.lv/cvs/mdocml/Makefile,v
retrieving revision 1.311
diff -u -r1.311 Makefile
--- Makefile 9 Feb 2011 10:03:02 -0000 1.311
+++ Makefile 24 Feb 2011 11:04:43 -0000
@@ -333,13 +333,13 @@
rm -f config.log
( cat config.h.pre; \
echo; \
- if $(CC) $(CFLAGS) -Werror -c test-strlcat.c >> config.log 2>&1; then \
+ if $(CC) $(CFLAGS) -Werror -o test-strlcat test-strlcat.c >> config.log 2>&1; then \
echo '#define HAVE_STRLCAT'; \
- rm test-strlcat.o; \
+ rm test-strlcat; \
fi; \
- if $(CC) $(CFLAGS) -Werror -c test-strlcpy.c >> config.log 2>&1; then \
+ if $(CC) $(CFLAGS) -Werror -o test-strlcpy test-strlcpy.c >> config.log 2>&1; then \
echo '#define HAVE_STRLCPY'; \
- rm test-strlcpy.o; \
+ rm test-strlcpy; \
fi; \
echo; \
cat config.h.post \
next reply other threads:[~2011-02-24 11:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 11:06 Kristaps Dzonsons [this message]
2011-02-24 11:35 ` Joerg Sonnenberger
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=4D663BCD.1000804@bsd.lv \
--to=kristaps@bsd.lv \
--cc=joerg@britannica.bec.de \
--cc=tech@mdocml.bsd.lv \
/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).