From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] jansson 2.11
Date: Tue, 11 Sep 2018 19:36:00 -0000 [thread overview]
Message-ID: <8faffa47-fc87-d170-382f-58946ac69ac8@cornell.edu> (raw)
In-Reply-To: <6449932f-b12b-03fd-c6ae-f046325e1131@gmail.com>
On 9/11/2018 2:58 PM, Marco Atzeri wrote:
> Am 11.09.2018 um 20:31 schrieb Ken Brown:
>> jansson is in Debian and Fedora:
>>
>> Â Â https://packages.debian.org/source/stretch/jansson
>> Â Â https://apps.fedoraproject.org/packages/jansson
>>
>> My cygport file is attached.
>>
>
> build fine but test fails as requires installation.
> If you add this, it will test without any installation
>
> src_test() {
> Â Â Â Â Â Â Â PATH=${B}/src/.libs/:${PATH}
> Â Â Â Â Â Â Â cd ${B}
> Â Â Â Â Â Â Â make -i check
> }
Thanks! I was wondering how to fix that. I previously did it the hard
way, by doing a separate in-tree build and running 'make check' there.
Ken
next prev parent reply other threads:[~2018-09-11 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 18:31 Ken Brown
2018-09-11 18:59 ` Marco Atzeri
2018-09-11 19:36 ` Ken Brown [this message]
2018-09-12 5:43 ` Marco Atzeri
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=8faffa47-fc87-d170-382f-58946ac69ac8@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@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).