public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: waterlan <waterlan@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: Cygwin needs a man-db port
Date: Thu, 24 Apr 2014 18:30:00 -0000	[thread overview]
Message-ID: <8149fda0a7a38274bc0e23ff09b4b1ea@xs4all.nl> (raw)
In-Reply-To: <5357D9AE.6060807@breisch.org>

Chris J. Breisch schreef op 2014-04-23 17:18:
> Chris J. Breisch wrote:
>> 
>> Check-0.9.12 seems to work out-of-the-box. Configure with 
>> --prefix=/usr.
>> 
>> "make check" on check reports all tests passed, despite what appear to
>> be some failures. The CHANGELOG says that this version should pass all
>> tests on Cygwin. I've just subscribed to the mailing list and will 
>> check
>> on whether these failures can be ignored or not. Still, it definitely
>> appears to work better than the version we have now, which only passes 
>> 1
>> test in the test suite.
> 
> Just to follow-up on this a bit more.
> 
> I misunderstood the results from check's check. I should learn just to
> trust the summary results. The tests passed.
>> 
>> Libpipeline-1.3.0 seems to work out-of-the-box. Configure with
>> --prefix=/usr.
>> 
>> Oddly a "make check" for libpipeline-1.3.0 doesn't appear to actually 
>> do
>> anything. This was not the case for earlier versions of libpipeline.
>> Well, that's one way of getting rid of the test failures, I guess.
>> 
> 
> I must have done something wrong in the build before I sent this.
> Re-building libpipeline does cause 'make check' to execute the tests.
> I got one failure. I've talked to the owner of the project, and he's
> sent me a patch that does eliminate the failure. So I now have a
> libpipeline where all tests pass under Cygwin.

Hi Chris,

Would you like to send the patch to me?


> I still get the shared library warnings when building man-db. I
> haven't yet investigated that.

regards,

-- 
Erwin Waterlander
http://waterlan.home.xs4all.nl/

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2014-04-24 18:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-24 20:29 How does Cygwin handle non-Latin1 man pages? (move to UTF-8?) Erwin Waterlander
2013-09-25 19:59 ` Erwin Waterlander
2013-09-25 20:10   ` Erwin Waterlander
2014-03-14 12:58     ` Cygwin needs a man-db port (was: How does Cygwin handle non-Latin1 man pages? (move to UTF-8?)) Erwin Waterlander
2014-03-14 13:52       ` Cygwin needs a man-db port Chris J. Breisch
2014-03-14 14:38         ` Erwin Waterlander
2014-03-14 15:52           ` Chris J. Breisch
2014-03-14 16:29             ` Erwin Waterlander
2014-03-14 17:05             ` Corinna Vinschen
2014-03-14 19:22               ` Chris J. Breisch
2014-03-16 11:43               ` Chris J. Breisch
2014-04-17 18:32       ` Chris J. Breisch
2014-04-20  6:41         ` Erwin Waterlander
2014-04-21 20:41         ` waterlan
2014-04-22  3:04           ` KIMURA Masaru
2014-04-23 15:18         ` Chris J. Breisch
2014-04-24 18:30           ` waterlan [this message]
2014-04-25  0:47             ` Chris J. Breisch
2014-04-24 19:43         ` waterlan
2014-04-24 22:10           ` waterlan
2014-04-30 16:49             ` waterlan

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=8149fda0a7a38274bc0e23ff09b4b1ea@xs4all.nl \
    --to=waterlan@xs4all.nl \
    --cc=cygwin@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).