From: Ingo Schwarze <schwarze@usta.de>
To: Thomas Klausner <wiz@netbsd.org>
Cc: discuss@mdocml.bsd.lv, joern.clausen@uni-bielefeld.de,
Michel Jansens <michel.jansens@ulb.ac.be>
Subject: Re: Solaris 10 issues with mdocml-1.12.3
Date: Sat, 9 Aug 2014 03:10:23 +0200 [thread overview]
Message-ID: <20140809011023.GB13540@iris.usta.de> (raw)
In-Reply-To: <20140710153917.GG517@danbala.tuwien.ac.at>
Hi,
Thomas Klausner wrote on Thu, Jul 10, 2014 at 05:39:17PM +0200:
> On Thu, Jul 10, 2014 at 02:40:33AM +0200, Thomas Klausner wrote:
>> pkgsrc got a bug report for mandoc not building on Solaris 10.
>> pkgsrc contains mdocml-1.12.3.
>>
>> Here's the bug report; questions about details please directly to Jörn.
>>
>> Furthermore, on pkgsrc-users, Michael Jansen hinted at a second problem:
>>
>> "-pkgin & pbulk don???t build because of textproc/mdocml (first a lack
>> of asprint, now a problem with BTREEINFO in apropos_db.c)"
I assume the problem with BTREEINFO will be gone in 1.13.1
because we no longer use Berkeley DB.
> Update from Michael: Builds now for him: "it appears that an upgrade
> from Solaris10 update 9 to Solaris10 update 11 on my pkgsrc zone is the
> reason mdocml now builds. It seems Oracle has implemented asprintf in
> latest release."
Good, so i understand there is nothing more to do here?
Of course, re-testing with mandoc-1.13.1-rc2 is very welcome!
Yours,
Ingo
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2014-08-09 1:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sfid-H20140710-024049-+045.48-1@spamfilter.osbf.lua>
2014-07-10 0:40 ` Thomas Klausner
2014-07-10 15:39 ` Thomas Klausner
2014-08-09 1:10 ` Ingo Schwarze [this message]
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=20140809011023.GB13540@iris.usta.de \
--to=schwarze@usta.de \
--cc=discuss@mdocml.bsd.lv \
--cc=joern.clausen@uni-bielefeld.de \
--cc=michel.jansens@ulb.ac.be \
--cc=wiz@netbsd.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).