public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: gnulib m4/threadlib.m4 bug crashing package tests
Date: Fri, 26 Nov 2021 13:17:13 -0500	[thread overview]
Message-ID: <f4870164-a56a-d1dd-51f9-f8786d358737@cornell.edu> (raw)
In-Reply-To: <b0feab96-0abd-733c-b1f7-31131a5e5aef@SystematicSw.ab.ca>

On 11/26/2021 12:34 PM, Brian Inglis wrote:
> On 2021-11-26 06:08, Ken Brown via Cygwin-apps wrote:
>> On 11/25/2021 1:25 PM, Yaakov Selkowitz via Cygwin-apps wrote:
>>> Add gl_cv_have_weak=no to cygconf?
>>
>> Are you suggesting maintainers should do this, or are you talking about 
>> patching cygport, like this:
>>
>> diff --git a/cygclass/autotools.cygclass b/cygclass/autotools.cygclass
>> index 712f437..8b6fdde 100644
>> --- a/cygclass/autotools.cygclass
>> +++ b/cygclass/autotools.cygclass
>> @@ -735,6 +735,14 @@ cygconf() {
>>                  export ac_cv_func_mmap_fixed_mapped=yes ;;
>>          esac
>>
>> +       # Some versions of gnulib's threadlib.m4:gl_WEAK_SYMBOLS
>> +       # incorrectly report that Cygwin supports weak symbols.  See
>> +       # https://cygwin.com/pipermail/cygwin-apps/2021-September/041587.html.
>> +       case ${CHOST} in
>> +       *-*-cygwin*)
>> +               export gl_cv_have_weak=no ;;
>> +       esac
>> +
>>          # packages that use intltool w/o glib-gettext get this wrong
>>          export DATADIRNAME="share"
> 
> Normally in a regular/autotools build the maintainer appends these overrides to:
> 
>      CYGCONF_ARGS=...gl_cv_have_weak=guessing\ no
> 
> or to:
> 
> src_compile() {
>          cd ${S}
>          cygautoreconf
>          cd ${B}
>      cygconf ... gl_cv_have_weak=guessing\ no
>          cygmake
> }

cygport already does this for ac_cv_func_mmap_fixed_mapped.  That's why I asked 
Yaakov to clarify what he had in mind.

Ken

  reply	other threads:[~2021-11-26 18:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-29 23:46 Brian Inglis
2021-11-25 16:26 ` Ken Brown
2021-11-25 18:25   ` Yaakov Selkowitz
2021-11-26  4:48     ` Brian Inglis
2021-11-26 13:08     ` Ken Brown
2021-11-26 17:34       ` Brian Inglis
2021-11-26 18:17         ` Ken Brown [this message]
2021-11-28 15:42     ` Achim Gratz
2021-11-28 15:56       ` Ken Brown
2021-11-28 16:33         ` Achim Gratz
2021-11-28 18:21           ` Ken Brown
2021-11-29 16:39             ` Achim Gratz
2021-12-08 18:49               ` Achim Gratz
2021-12-09  4:41                 ` Brian Inglis
2021-11-28 16:23       ` Achim Gratz
2021-11-28 18:34         ` Brian Inglis
2021-11-29 17:38           ` Achim Gratz

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=f4870164-a56a-d1dd-51f9-f8786d358737@cornell.edu \
    --to=kbrown@cornell.edu \
    --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).