From: Marco Atzeri <marco.atzeri@gmail.com>
To: Jon Turney <jon.turney@dronecode.org.uk>
Cc: cygwin-apps@cygwin.com
Subject: Re: scallyweg: ‘strcasecmp’ was not declared in this scope
Date: Sat, 2 Mar 2024 18:01:59 +0100 [thread overview]
Message-ID: <794652b4-a9ff-430f-a956-bddc19d89fb1@gmail.com> (raw)
In-Reply-To: <f888a928-f17a-4e19-bb4d-a2630eab7633@dronecode.org.uk>
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
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
Regards
Marco
next prev parent reply other threads:[~2024-03-02 17:02 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 [this message]
2024-03-03 14:27 ` Jon Turney
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=794652b4-a9ff-430f-a956-bddc19d89fb1@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-apps@cygwin.com \
--cc=jon.turney@dronecode.org.uk \
/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).