From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: pdfgrep [ITA]
Date: Sun, 9 May 2021 21:54:57 +0200 [thread overview]
Message-ID: <e1410073-59aa-acec-1905-69d7b4aab420@gmail.com> (raw)
In-Reply-To: <017801d74500$4c5eb270$e51c1750$@pdinc.us>
On 09.05.2021 20:22, Jason Pyeron wrote:
>>>
>>> pull it up to the latest version (2.1.2),
>
> 2 Issues encountered and mitigated.
>
> 1. There are some significant changes in the functionality of 2.1.2 vs 1.4.1.
> 2. The tool chain has evolved a bit since 2016, so the current 1.4.1-1 release would not build anymore, so I have updated the cygport as release 2.
>
> So I have built both 1.4.1 and 2.1.2 on Windows Server 2019 with all updates installed.
>
>>> check the patches for the
>>> major Linux distros (if any, Fedora does not for instance) and make sure
>
> I started with pdfgrep's master branch, so when the next release is made there should not be any surprises. But I did not yet review other distro's patches. I can make master branch builds available as test marked packages, but need guidance on version number and release numbering first.
>
> I have not pushed my changes outside of my private repo, as I expect that there will be some editorial change requests along with any additional patching.
>
>>> it works on both 32bit and 64bit architecture and show the result.
>
> How should I force cygport to run `make check`? In other words how do I link the `cygport test` command to `make check` ? I read the cygport docs, but README and html/manual/src_test_cygpart.html were not helpful.
>
`cygport pdfgrep.cygport check` will run make check.
the default test method is
src_test() {
cd ${B}
cygmake check
}
On my build, it is all failing
and the binary itself is not really functional
$ ./pdfgrep.exe --help
terminate called after throwing an instance of 'std::runtime_error'
what(): locale::facet::_S_create_c_locale name not valid
Aborted (core dumped)
Same for your binary
May be some other patches are needed ?
General suggestion:
- add BUILD_REQUIRES="libpcre-devel libgcrypt-devel libpoppler-cpp-devel"
the test suite seems to need tcl so you may need to add more packages
next prev parent reply other threads:[~2021-05-09 19:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 19:10 Jason Pyeron
2021-05-03 19:21 ` Achim Gratz
2021-05-03 19:28 ` Jason Pyeron
[not found] ` <001001d74052$710751c0$5315f540$@pdinc.us>
2021-05-09 18:22 ` Jason Pyeron
2021-05-09 18:58 ` Achim Gratz
2021-05-09 19:54 ` Marco Atzeri [this message]
2021-05-09 20:05 ` Marco Atzeri
2021-05-09 21:12 ` Jason Pyeron
2021-05-10 6:35 ` Marco Atzeri
2021-05-12 9:27 ` Marco Atzeri
2021-05-17 5:00 ` Jason Pyeron
2021-05-17 6:28 ` Marco Atzeri
2021-05-17 19:59 ` Jason Pyeron
2021-05-18 9:10 ` Marco Atzeri
2021-05-18 17:13 ` Achim Gratz
2021-05-18 19:24 ` Jason Pyeron
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=e1410073-59aa-acec-1905-69d7b4aab420@gmail.com \
--to=marco.atzeri@gmail.com \
--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).