From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Cc: waterlan@xs4all.nl
Subject: Re: some libunistring 1.0 tests are core dumping on github build
Date: Sun, 30 Oct 2022 09:56:04 -0600 [thread overview]
Message-ID: <1321144f-a7ad-367e-d4a3-09424eb4a202@SystematicSw.ab.ca> (raw)
On Wed, 19 Oct 2022 16:55:43 +0200 (CEST), Erwin Waterlander wrote:
> I uploaded a new cyport file for libunistring 1.0. I got a failed build,
> because several tests core dumped. This does not happen when I run the tests
> on my PC. What to do next?
> See https://github.com/cygwin/scallywag/actions/runs/3252280207
I recently did personal local and Scallywag builds of libunistring to check
updated Unicode support for my package builds: see libunistring DEPENDENCIES and
HACKING for build and test prereqs.
I decided to build and package embedded unistring (from updated gnulib included
in package) for updated Unicode support.
Missing DEPEND/BUILD_REQUIRES definitions in libunistring.cygport gives prereq
packages required which will be pre-installed to build and test under Scallywag:
# old var
DEPEND="libiconv-devel"
DEPEND+=" autoconf automake diffutils gawk gcc-core gperf grep"
DEPEND+=" m4 make perl pkg-config sed texinfo-tex texlive"
or
# new var
BUILD_REQUIRES="libiconv-devel"
BUILD_REQUIRES+=" autoconf automake diffutils gawk gcc-core gperf grep"
BUILD_REQUIRES+=" m4 make perl pkg-config sed texinfo-tex texlive"
Only some standard prereq packages (like "build-essential") are pre-installed as
cygport dependencies that it uses and knows its cygparts and cygclasses need
like autotools binutils coreutils, etc.
But it's good practice to define *ALL* the Cygwin packages containing specified
prereq devel libraries and build tools required to build and test the package
(and subpackages).
You also have to install and define any perl, python, ruby, etc. module packages
required at build *OR* runtime so cygport can identify them correctly and you
don't then need to manually specify REQUIRES=... module packages.
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next reply other threads:[~2022-10-30 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 15:56 Brian Inglis [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-19 14:55 Erwin Waterlander
2022-10-30 13:15 ` Jon Turney
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=1321144f-a7ad-367e-d4a3-09424eb4a202@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-apps@cygwin.com \
--cc=waterlan@xs4all.nl \
/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).