Date: Fri, 12 Sep 2025 11:19:54 +0100 From: Bob Bishop <rb@gid.co.uk> To: Olivier Certner <olce@FreeBSD.org> Cc: FreeBSD Current <freebsd-current@FreeBSD.org>, Alan Somers <asomers@FreeBSD.org>, Toomas Soome <tsoome@me.com> Subject: Re: git: d549de769055 - main - libc: Remove readdir_r(3) [This broke building rust 1.88] Message-ID: <0F481EDD-24F4-4F2C-BCBB-9B016DD313F3@gid.co.uk> In-Reply-To: <4148862.BRNeRiNLvY@ravel> References: <C79DD894-11FD-4919-B3EE-147978D36AF8@me.com> <CAOtMX2gS54kMJMsudth5AzCSWzELgP5o8%2B8gQ5ac2P3mcSVG%2BA@mail.gmail.com> <4148862.BRNeRiNLvY@ravel>
index | next in thread | previous in thread | raw e-mail
Hi, > On 12 Sep 2025, at 09:09, Olivier Certner <olce@FreeBSD.org> wrote: > >> That should certainly be done. I'll try to do it this weekend, if I have >> time. However, the need to revert this change will remain. FreeBSD 15 >> needs the ability to run both current and old Rust toolchains. > > Yes, and adding to that that I don't see any pressing reason to get rid of readdir_r(), knowing a bit or two on that topic, irrespective of what Rust will or will not do in the short/middle-term. Not detailing anything more here, as I already did in https://reviews.freebsd.org/D52474 where I think this discussion should continue. > Thanks and regards. +1 And while I’m here, POSIX.1 defines for readdir_r (and readdir): [EOVERFLOW] One of the values in the structure to be returned cannot be represented correctly. …which I think would cover the case of indeterminate NAME_MAX/PATH_MAX for readdir_r. Also while I’m here, isn’t ESTALE a possibility for readdir/readdir_r on an NFS volume? > -- > Olivier Certner -- Bob Bishop rb@gid.co.ukhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0F481EDD-24F4-4F2C-BCBB-9B016DD313F3>