From: Jon Turney <jon.turney@dronecode.org.uk>
To: Marco Atzeri <marco.atzeri@gmail.com>
Cc: cygwin-apps@cygwin.com
Subject: Re: scallyweg: ‘strcasecmp’ was not declared in this scope
Date: Sun, 3 Mar 2024 14:27:43 +0000 [thread overview]
Message-ID: <d265414f-d091-41e5-aad7-04aec52dc523@dronecode.org.uk> (raw)
In-Reply-To: <794652b4-a9ff-430f-a956-bddc19d89fb1@gmail.com>
On 02/03/2024 17:01, Marco Atzeri via Cygwin-apps wrote:
> On 29/02/2024 17:58, Jon Turney wrote:
>> On 29/02/2024 06:21, Marco Atzeri via Cygwin-apps wrote:
>>> Hi Jon,
>>>
>>> I have a strange case with nco
>>>
>>> https://github.com/cygwin/scallywag/actions/runs/8060036334/job/22015501908
>>>
>>> While Scallyweg complains about ‘strcasecmp’ scope,
>>> local build runs fine.
>>> I saw the same also on previous build
>>>
>>> Can you check ?
>>
>> I can reproduce the build failure locally.
>>
>> From a brief inspection, this seems to make sense: strcasecmp is
>> unconditionally defined by strings.h, which doesn't seem to be
>> included anywhere in antlr.
>>
>> (There's maybe some way it gets indirectly included, maybe via
>> string.h if __BSD_VISIBLE, but perhaps that's due to some local flags
>> settings?)
>>
>
> thanks for double checking
No problem.
> The problem was subtle; the original and ancient
>
> https://www.antlr2.org/download/antlr-2.7.7.tar.gz
>
> need patching to work with recent compiler.
> I had a different version, with the same name, on my computer
> but I forgot to update the SRC_URI, so me locally and scallyweg were
> working on different source packages.
>
> Further info on:
> https://nco.sourceforge.net/#Source
Aha! Two archives with the same name but different contents, always great.
There really ought to be a list of hashes for SRC_URI files associated
with a .cygport file, and cygport should verify them after downloading
(which would avoid this problem, and related ones), but we've needed
that feature for a while...
prev parent reply other threads:[~2024-03-03 14:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 6:21 Marco Atzeri
2024-02-29 16:58 ` Jon Turney
2024-03-02 17:01 ` Marco Atzeri
2024-03-03 14:27 ` Jon Turney [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=d265414f-d091-41e5-aad7-04aec52dc523@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
--cc=marco.atzeri@gmail.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).