From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: Cygwin Applications <cygwin-apps@cygwin.com>
Subject: Re: scallywag zp_texlive_finish.dash failing exit code 2 rebuilding installed formats
Date: Sun, 22 Aug 2021 09:21:11 -0600 [thread overview]
Message-ID: <6f14abfb-bafa-7bf8-d01f-c572381322da@SystematicSw.ab.ca> (raw)
In-Reply-To: <6a370b1b-49e7-3207-e89c-e9b28c3f3423@SystematicSw.ab.ca>
On 2021-08-21 18:48, Brian Inglis wrote:
> Any way to see if there is anything useful in scallywag #160 (3181)
> fontconfig run 1154600337 build_requires setup /var/log/setup.log.full
> without hacking and pushing fontconfig.cygport?
>
> https://github.com/cygwin/scallywag/actions/runs/1154600337/workflow
>
> Trying to build updated fontconfig (to see if continual cache creation
> issue has been resolved, or analyze and hopefully debug that issue to
> remove or patch the cause, then ITA), but getting weird build issues.
>
> Trying scallywag playground, but it's also having problems installing
> prereq texlive-collection-htmlxml, which pulls in other packages
> including texlive-collection-formatsextra, which need built by
> /etc/postinstall/zp_texlive_finish.dash, which is failing somewhere with
> exit code 2 - not a lot of detail!
Looks like for some reason, even after autoreconf, and the build
generating cygfontconfig-1.dll, it thinks it is building native Windows
programs and generates /usr/lib/libfontconfig.def, fontconfig.pc
contains "cachedir=LOCAL_APPDATA_FONTCONFIG_CACHE", obviously not
%-enclosed or expanded, and test programs are linked with
libfontconfig-1.dll:
C:/.../fontconfig-2.13.94-1.x86_64/build/test/.libs/test-bz106618.exe:
error while loading shared libraries: libfontconfig-1.dll: cannot open
shared object file: No such file or directory
Hopefully someone has seen this behaviour before, and can help suggest
an approach to fix the build.
The issue may relate to using a new m4 test release, or missing Cygwin
bits in gnulib, aclocal, dlltool, or libtool.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
prev parent reply other threads:[~2021-08-22 15:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-22 0:48 Brian Inglis
2021-08-22 15:15 ` Jon Turney
2021-08-22 15:33 ` Brian Inglis
2021-08-22 21:57 ` Brian Inglis
2021-08-22 22:38 ` Ken Brown
2021-08-22 22:58 ` Ken Brown
2021-08-23 18:46 ` Brian Inglis
2021-08-23 21:08 ` Ken Brown
2021-08-24 0:26 ` Brian Inglis
2021-08-24 14:57 ` Ken Brown
2021-08-24 17:17 ` Brian Inglis
2021-08-22 22:20 ` /etc/postinstall/zp_texlive_finish.dash fails missing marvosysm.sty Brian Inglis
2021-08-22 22:26 ` Brian Inglis
2021-08-22 15:21 ` Brian Inglis [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=6f14abfb-bafa-7bf8-d01f-c572381322da@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).