From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: expat update would be good
Date: Sun, 5 Mar 2023 21:25:17 +0100 [thread overview]
Message-ID: <ffd8846a-e7bf-9470-1c1e-bc180895d853@gmail.com> (raw)
In-Reply-To: <0042d2ab-c400-bd1c-2d67-6498e21d7237@Shaw.ca>
On 05.03.2023 20:24, Brian Inglis via Cygwin wrote:
> [Xpost to cygwin in case apps not monitored]
> On 2023-03-05 08:00, Marco Atzeri via Cygwin-apps wrote:
>> On 13.02.2022 21:34, Brian Inglis wrote:
>>> [posting to apps to be less public]
>>> https://nvd.nist.gov/vuln/detail/CVE-2022-23990
>>> expat < 2.4.4
>
>> ping ?
>> In addition the cmake import library have some issues also
>
> Been a year since I hinted!
>
> Fixed releases build okay for me 2.4.1/5/9 up to current 2.5.0.
> See:
>
> https://cygwin.com/cgi-bin2/jobs.cgi?id=5541
> https://github.com/cygwin/scallywag/actions/runs/4337543797
> https://github.com/cygwin/scallywag/actions/runs/4337543797/jobs/7573650090
>
> What are you seeing?
>
building latest gdal I was forced to add a line on expact.c
$ grep private /usr/lib/pkgconfig/expat.pc
Libs.private: -liconv
and move away
/usr/lib/make/expat-2.4.1
as the settings are wrong and cmake complains about missing files
$ grep -H "so.1" *.cmake
expat-noconfig.cmake: IMPORTED_LOCATION_NOCONFIG
"${_IMPORT_PREFIX}/lib/libexpat.so.1.8.1"
expat-noconfig.cmake: IMPORTED_SONAME_NOCONFIG "libexpat.so.1"
expat-noconfig.cmake:list(APPEND _IMPORT_CHECK_FILES_FOR_expat::expat
"${_IMPORT_PREFIX}/lib/libexpat.so.1.8.1" )
If Doug does not reply, are you considering to adopt expat ?
Regards
Marco
next prev parent reply other threads:[~2023-03-05 20:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ba8154f2-b404-6f7e-af3b-b8b1af35f990@SystematicSw.ab.ca>
[not found] ` <de1678c2-e0a0-0cf2-3ff1-f0b558233ab5@gmail.com>
2023-03-05 19:24 ` Brian Inglis
2023-03-05 20:25 ` Marco Atzeri [this message]
2023-03-05 23:08 ` Brian Inglis
2023-03-06 6:03 ` 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=ffd8846a-e7bf-9470-1c1e-bc180895d853@gmail.com \
--to=marco.atzeri@gmail.com \
--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).