From: Peter Korsgaard <peter@korsgaard.com>
To: yegorslists@googlemail.com
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/ncftp: fix incompatible-pointer-types error
Date: Mon, 03 Mar 2025 20:49:29 +0100 [thread overview]
Message-ID: <8734ftnbcm.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20250303144047.268530-1-yegorslists@googlemail.com> (yegorslists@googlemail.com's message of "Mon, 3 Mar 2025 15:40:47 +0100")
>>>>> "yegorslists" == yegorslists <yegorslists@googlemail.com> writes:
> From: Yegor Yefremov <yegorslists@googlemail.com>
> Use only stat, fstat, and lstat structures for the correspondent calls
> and let the C library macros to pick the right structure and call
> depending on the supported file size.
Do we have any autobuilder errors from this?
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> ---
> package/ncftp/0003-fix-stat.patch | 27 +++++++++++++++++++++++++++
> 1 file changed, 27 insertions(+)
> create mode 100644 package/ncftp/0003-fix-stat.patch
> diff --git a/package/ncftp/0003-fix-stat.patch b/package/ncftp/0003-fix-stat.patch
> new file mode 100644
> index 0000000000..8581cf546b
> --- /dev/null
> +++ b/package/ncftp/0003-fix-stat.patch
> @@ -0,0 +1,27 @@
> +Use stat, fstat, and lstat structures and let the C library handle the
> +related structures and system calls.
> +
> +Upstream: N/A, unresponsive contact email address.
If upstream is dead, perhaps we should instead drop the ncftp package
given how little FTP is used nowadays?
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-03-03 19:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 14:40 [Buildroot] [PATCH] package/ncftp: fix incompatible-pointer-types error yegorslists
2025-03-03 14:43 ` Yegor Yefremov
2025-03-03 19:49 ` Peter Korsgaard [this message]
2025-03-25 22:01 ` Julien Olivain
2025-03-25 22:17 ` Yegor Yefremov via buildroot
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=8734ftnbcm.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=yegorslists@googlemail.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