From: "LÉVAI Dániel" <leva@ecentrum.hu>
To: Ingo Schwarze <schwarze@usta.de>
Cc: discuss@mdocml.bsd.lv
Subject: Re: "cannot parse date" for a seemingly valid .Dd parameter
Date: Thu, 28 Aug 2014 20:06:17 +0200 [thread overview]
Message-ID: <20140828180617.GA15202@serenity.local> (raw)
In-Reply-To: <20140828173522.GT912@iris.usta.de>
On cs, aug 28, 2014 at 19:35:22 +0200, Ingo Schwarze wrote:
> Hi Daniel,
>
> LÉVAI Dániel wrote on Thu, Aug 28, 2014 at 06:32:15PM +0200:
>
> > So here are the new outputs of the given commands:
> >
> > $ ./configure
> [...]
> > wchar: yes
>
> Good.
>
> > manpath: no
>
> By the way, that is odd. Given that the bug hides so skillfully,
> i'd like to pay attention to any clue. You say you are on Linux?
Yes, this is on Linux; a slightly modified version of Slackware.
> Can you show the output of:
>
> $ manpath
> $ which manpath
> $ man -w manpath
Actually, there is no manpath binary on my system, nor manual page for
it.
> $ ls -ald /etc/man*
-rw-r--r-- 1 root root 4729 2014-08-20 17.02.35 /etc/man.conf
-rw-r--r-- 1 root root 2038 2014-08-20 15.39.26 /etc/mandoc.conf
> $ man -w man.conf
/usr/man/man5/man.conf.5.gz
> $ man -V
man, version 1.6g
> So even though we haven't found your bug yet, your report already
> resulted in one useful bugfix.
Alright! :-)
> > "Unfortunately", CVS HEAD still doesn't emit my original problem
> > when using '-Tlint'.
>
> So we have no choice but to retry with 1.13.1. Please go to your
> checkout area and do this:
>
> $ cvs up -C
> $ cvs up -r VERSION_1_13_1
> $ patch < tmp.patch # the debug patch appended below (for 1.13.1)
> $ make clean
> $ make
Because for a second I thought I was hallucinating (again.. :P), 'cause
I've compile the 1_13_1 tag and the problem was not there, then checked
with the 1.13.1 release tarball, and it was not there either, I dug
deeper and turns out, that with these latest tests, I didn't use my
usual CFLAGS during the compilation. And the culprit for me seems to be:
$ cvs up -rVERSION_1_13_1
$ CFLAGS='-DOSNAME=\"Slackware\ Linux\"' make
...
$ ./mandoc -Tlint test.1
mandoc: ../mdocml/test.1:1:2: WARNING: cannot parse date, using it verbatim: August 27, 2014
Without the -DOSNAME define, it doesn't emit this warning. I know I'm
not crazy! Sort of... :)
Sorry for not posting the exact steps I've been using to compile
mdocml... rookie mistake..
>
> And then we need the usual sequence of commands again...
$ ./mandoc -Wall test.1 > /dev/null
main: LC_TIME = C
a2time: LC_TIME = C
a2time: LC_TIME = C
a2time: LC_TIME = C
mandoc: test.1:1:2: WARNING: cannot parse date, using it verbatim: August 27, 2014
$ ./mandoc -Wall -Tlocale test.1 > /dev/null
main: LC_TIME = C
a2time: LC_TIME = C
a2time: LC_TIME = C
a2time: LC_TIME = C
mandoc: test.1:1:2: WARNING: cannot parse date, using it verbatim: August 27, 2014
ascii_init: LC_TIME = C
ascii_init: LC_TIME = hu_HU.UTF-8
config.h:
===================8<===================
#ifndef MANDOC_CONFIG_H
#define MANDOC_CONFIG_H
#if defined(__linux__) || defined(__MINT__)
# define _GNU_SOURCE /* getsubopt(), strcasestr(), strptime() */
#endif
#include <sys/types.h>
#include <stdio.h>
#define VERSION "1.13.1"
#if !defined(__BEGIN_DECLS)
# ifdef __cplusplus
# define __BEGIN_DECLS extern "C" {
# else
# define __BEGIN_DECLS
# endif
#endif
#if !defined(__END_DECLS)
# ifdef __cplusplus
# define __END_DECLS }
# else
# define __END_DECLS
# endif
#endif
#ifndef HAVE_FGETLN
extern char *fgetln(FILE *, size_t *);
#endif
#ifndef HAVE_GETSUBOPT
extern int getsubopt(char **, char * const *, char **);
extern char *suboptarg;
#endif
#ifndef HAVE_REALLOCARRAY
extern void *reallocarray(void *, size_t, size_t);
#endif
#ifndef HAVE_SQLITE3_ERRSTR
extern const char *sqlite3_errstr(int);
#endif
#ifndef HAVE_STRCASESTR
extern char *strcasestr(const char *, const char *);
#endif
#ifndef HAVE_STRLCAT
extern size_t strlcat(char *, const char *, size_t);
#endif
#ifndef HAVE_STRLCPY
extern size_t strlcpy(char *, const char *, size_t);
#endif
#ifndef HAVE_STRSEP
extern char *strsep(char **, const char *);
#endif
#endif /* MANDOC_CONFIG_H */
===================8<===================
But regarding CVS HEAD, even with the OSNAME define, it won't tell me
that warning.
Daniel
--
LÉVAI Dániel
PGP key ID = 0x83B63A8F
Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2014-08-28 18:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 14:58 LÉVAI Dániel
2014-08-27 15:07 ` Kristaps Dzonsons
2014-08-27 15:15 ` LÉVAI Dániel
2014-08-28 0:43 ` Ingo Schwarze
2014-08-28 8:39 ` LÉVAI Dániel
2014-08-28 16:11 ` Ingo Schwarze
2014-08-28 16:32 ` LÉVAI Dániel
2014-08-28 17:35 ` Ingo Schwarze
2014-08-28 18:06 ` LÉVAI Dániel [this message]
2014-08-28 19:49 ` Ingo Schwarze
2014-08-28 21:07 ` LÉVAI Dániel
2014-08-29 15:38 ` Ingo Schwarze
2014-08-30 8:57 ` LÉVAI Dániel
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=20140828180617.GA15202@serenity.local \
--to=leva@ecentrum.hu \
--cc=discuss@mdocml.bsd.lv \
--cc=schwarze@usta.de \
/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).