From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.13]) by sourceware.org (Postfix) with ESMTPS id C50153857C40 for ; Tue, 11 Aug 2020 22:00:42 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org C50153857C40 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=SystematicSw.ab.ca Authentication-Results: sourceware.org; spf=none smtp.mailfrom=brian.inglis@systematicsw.ab.ca Received: from [192.168.1.104] ([24.64.172.44]) by shaw.ca with ESMTP id 5cK0krNJHng7K5cK1kGtMj; Tue, 11 Aug 2020 16:00:41 -0600 X-Authority-Analysis: v=2.3 cv=ecemg4MH c=1 sm=1 tr=0 a=kiZT5GMN3KAWqtYcXc+/4Q==:117 a=kiZT5GMN3KAWqtYcXc+/4Q==:17 a=IkcTkHD0fZMA:10 a=kPCIzciLAAAA:20 a=Ed7FdIT4gc43trk-okQA:9 a=QEXdDO2ut3YA:10 Reply-To: cygwin@cygwin.com Subject: Re: [ANNOUNCEMENT] Updated: curl 7.71.1-1 To: cygwin@cygwin.com References: <4f1d6241-c86b-f2f9-7b49-a9f5b998b0eb@SystematicSw.ab.ca> <53c7f2a7-3bd8-f90c-b574-969d6b31f300@cornell.edu> <71031f78-b1be-aec2-4e54-72ff49e07543@SystematicSw.ab.ca> <11d99d00-55fb-f6a2-893d-f5ebb6e7a14b@cornell.edu> From: Brian Inglis Autocrypt: addr=Brian.Inglis@SystematicSw.ab.ca; prefer-encrypt=mutual; keydata= mDMEXopx8xYJKwYBBAHaRw8BAQdAnCK0qv/xwUCCZQoA9BHRYpstERrspfT0NkUWQVuoePa0 LkJyaWFuIEluZ2xpcyA8QnJpYW4uSW5nbGlzQFN5c3RlbWF0aWNTdy5hYi5jYT6IlgQTFggA PhYhBMM5/lbU970GBS2bZB62lxu92I8YBQJeinHzAhsDBQkJZgGABQsJCAcCBhUKCQgLAgQW AgMBAh4BAheAAAoJEB62lxu92I8Y0ioBAI8xrggNxziAVmr+Xm6nnyjoujMqWcq3oEhlYGAO WacZAQDFtdDx2koSVSoOmfaOyRTbIWSf9/Cjai29060fsmdsDLg4BF6KcfMSCisGAQQBl1UB BQEBB0Awv8kHI2PaEgViDqzbnoe8B9KMHoBZLS92HdC7ZPh8HQMBCAeIfgQYFggAJhYhBMM5 /lbU970GBS2bZB62lxu92I8YBQJeinHzAhsMBQkJZgGAAAoJEB62lxu92I8YZwUBAJw/74rF IyaSsGI7ewCdCy88Lce/kdwX7zGwid+f8NZ3AQC/ezTFFi5obXnyMxZJN464nPXiggtT9gN5 RSyTY8X+AQ== Organization: Systematic Software Message-ID: <8c14a6d0-7c52-ee29-5026-a306166c2e87@SystematicSw.ab.ca> Date: Tue, 11 Aug 2020 16:00:40 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-CA Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfNwTwmWUnTWr4orXB3JOXMr7+qA2t+dpTDeQ1jiKWcCCEbSsCfNvesXGSWPEJQp3D947+4YDGgNH9dyu+2WWHiWsOF+htrsM+A5WQ34NtNlYTo1IY2xI BHX5+NALRvt778UKz6o5lOzmdo2NRl8EleLKM1L3QwQKJaAXiXQYKrkMsD649ITbC7p4SYJzgvt36g== X-Spam-Status: No, score=-7.4 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, KAM_NUMSUBJECT, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Aug 2020 22:00:44 -0000 On 2020-08-11 05:27, Adam Dinwoodie wrote: > On Tue, 11 Aug 2020 at 12:14, Ken Brown via Cygwin wrote: >>> In that case, it looks to me as if the generated curl-config --libs statements: >>> >>> if test "Xyes" = "Xno" -o "Xyes" = "Xyes"; then >>> echo ${CURLLIBDIR}-lcurl -lnghttp2 -lidn2 -lssh -lpsl -lssl -lcrypto >>> -lldap -llber -lbrotlidec -lbrotlidec -lz >>> >>> based on curl-config.in: >>> >>> if test "X@ENABLE_SHARED@" = "Xno" -o "X@REQUIRE_LIB_DEPS@" = "Xyes"; then >>> echo ${CURLLIBDIR}-lcurl @LIBCURL_LIBS@ >>> >>> REQUIRE_LIB_DEPS should be no, derived from configure.ac: >>> >>> if test "X$enable_shared" = "Xyes" -a "X$link_all_deplibs" = "Xno" >>> then >>> REQUIRE_LIB_DEPS=no >>> else >>> REQUIRE_LIB_DEPS=yes >>> fi >>> AC_SUBST(REQUIRE_LIB_DEPS) >>> AM_CONDITIONAL(USE_EXPLICIT_LIB_DEPS, test x$REQUIRE_LIB_DEPS = xyes) >>> >>> but for Cygwin link_all_deplibs remains defaulted to unknown, so either that >>> variable should be set in configure, or that condition should perhaps be changed >>> to: >>> >>> if test "X$enable_shared" = "Xyes" -a "X$link_all_deplibs" != "Xyes" >>> >>> with appropriate bug reports and changes to be made upstream if possible. >> >> If you want to look into ways of fixing curl-config different from what Yaakov >> did, that's fine; you're the maintainer. All I did was look at Yaakov's patch >> and port it to curl 7.71.1, that being a quick and easy way to fix the reported >> problem. > > Someone else did raise this problem upstream at > https://github.com/curl/curl/issues/5793, and the comments there imply > they'd be interested in integrating patches Cygwin uses into the > upstream code, although the upstream maintainers aren't going to do > that without someone proactively submitting the patch to them. I'll copy these comments and suggestions and follow up there, as that appears to be the official bug tracker, and they appear receptive to discussing and fixing issues. > For my part, I'm not particularly fussed whether this is fixed with an > upstream patch or a Cygwin patch; I just want my use cases to work, > and as of 7.71.1-1 they don't. That said, my experience of being a > package maintainer would lead me to want to submit patches upstream if > at all possible, just to reduce the need to handle these sorts of > problems. My inclination would be to restore the patched behaviour > with Ken's new patch as a short-term fix, then get this submitted > upstream so that in the long-term this patch can be retired. I did not see or get your original email, and could not reproduce your issue using the current git source package, curl package, and cygport. That could be due to two missing perl modules (solved in another sub-thread by Achim). Any suggestions as to what may be required to get curl-config to act up in a build would be appreciated. It is always easier to check if a problem is actually fixed when you can perform an in situ regression test. Running curl-config and reading the docs, it does not appear to me to be clearly specified why and when dynamic and static library parameters are either built in or generated, whereas the conditions for reproducing the output are well specified for pkgconf/pkg-config. That may become more apparent in follow ups on the bug tracker. -- 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 IEC units and prefixes, physical quantities in SI.]