From: Svyatoslav Mishyn <juef@openmailbox.org>
To: discuss@mdocml.bsd.lv
Subject: Re: texi2mdoc
Date: Wed, 25 Feb 2015 19:23:32 +0200 [thread overview]
Message-ID: <20150225172330.GA1566@k8> (raw)
In-Reply-To: <54EDE7A2.9020001@bsd.lv>
(Wed, 25 Feb 16:17) Kristaps Dzonsons:
> Hi,
>
> All of the raised concerns are part of the new release, 0.1.2.
>
> http://mdocml.bsd.lv/texi2mdoc
>
Hello,
Now I'm experimenting to compile against musl [0] (via musl-gcc wrapper) :)
texi2mdoc is interesting for me just because I still trying to learn C.
and I like small and beautiful programs
BTW: Why all files extracted from tarball read-only,
not for example, -rw-rw-r-- ?
/home/juef/dl/texi2mdoc-0.1.2: make CC=musl-gcc
musl-gcc -g -W -Wall -Wstrict-prototypes -Wno-unused-parameter
-Wwrite-strings -c -o main.o main.c
In file included from main.c:32:0:
extern.h:397:1: error: expected '=', ',', ';', 'asm' or '__attribute__'
before 'void'
void advance(struct texi *, size_t *);
^
main.c:35:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before
'static'
static const char *const sects[SECTSZ] = {
^
main.c: In function 'dodefindex':
main.c:352:3: warning: implicit declaration of function 'advance'
[-Wimplicit-function-declaration]
advance(p, pos);
^
main.c: In function 'dosubsubsection':
main.c:1503:19: error: 'sects' undeclared (first use in this function)
teximacroopen(p, sects[sec]);
^
main.c:1503:19: note: each undeclared identifier is reported only once for
each function it appears in
main.c:1497:7: warning: variable 'sec' set but not used
[-Wunused-but-set-variable]
int sec;
^
main.c: In function 'dosubsection':
main.c:1517:45: error: 'sects' undeclared (first use in this function)
texierr(p, "\"%s\" in open line scope!?", sects[sec]);
^
main.c: In function 'dosection':
main.c:1564:45: error: 'sects' undeclared (first use in this function)
texierr(p, "\"%s\" in open line scope!?", sects[sec]);
^
main.c:1544:8: warning: variable 'sec' set but not used
[-Wunused-but-set-variable]
int sec;
^
<builtin>: recipe for target 'main.o' failed
make: *** [main.o] Error 1
[0]: http://www.musl-libc.org/
--
http://www.juef.tk/
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2015-02-25 17:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 15:31 texi2mdoc Kristaps Dzonsons
2015-02-23 16:56 ` texi2mdoc Svyatoslav Mishyn
2015-02-23 17:31 ` texi2mdoc Kristaps Dzonsons
2015-02-23 18:13 ` texi2mdoc Ingo Schwarze
2015-02-23 18:17 ` texi2mdoc Svyatoslav Mishyn
2015-02-25 15:17 ` texi2mdoc Kristaps Dzonsons
2015-02-25 17:23 ` Svyatoslav Mishyn [this message]
2015-02-25 19:50 ` texi2mdoc Kristaps Dzonsons
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=20150225172330.GA1566@k8 \
--to=juef@openmailbox.org \
--cc=discuss@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).