Re: clang 15 and zlib

2023-09-05 Thread Todd C . Miller
On Wed, 06 Sep 2023 10:43:34 +1000, Jonathan Gray wrote: > tb updated us to the newer version a while ago OK millert@ - todd

Re: clang 15 and zlib

2023-09-05 Thread Theo Buehler
On Wed, Sep 06, 2023 at 10:43:34AM +1000, Jonathan Gray wrote: > On Wed, Dec 28, 2022 at 02:36:56PM -0700, Todd C. Miller wrote: > > OK millert@ as well. There is no point in trying to fix this locally > > when upstream zlib will be changing it in the near(?) future. > > > > - todd > > tb updat

Re: clang 15 and zlib

2023-09-05 Thread Jonathan Gray
On Wed, Dec 28, 2022 at 02:36:56PM -0700, Todd C. Miller wrote: > OK millert@ as well. There is no point in trying to fix this locally > when upstream zlib will be changing it in the near(?) future. > > - todd tb updated us to the newer version a while ago diff --git sys/arch/amd64/conf/Makefi

Re: clang 15 and zlib

2022-12-31 Thread Theo de Raadt
A third alternative is to change the clang default to not be so aggressive. Why is that option not on the list of choices we have? This is causing so much chaos in our base tree. Is there an assumption this will be roses and daisies when these new default options start chewing on the ports free?

Re: clang 15 and zlib

2022-12-29 Thread Jeremie Courreges-Anglas
On Wed, Dec 28 2022, Jeremie Courreges-Anglas wrote: > To build src cleanly with clang-15 you'd need the diff below. The > alternative would be to patch our three zlib copies and wait for > upstream to fix it. A more comfortable alternative is to just neuter > the warning. -Wno-unknown-warning-

Re: clang 15 and zlib

2022-12-28 Thread Damien Miller
On Wed, 28 Dec 2022, Todd C. Miller wrote: > OK millert@ as well. There is no point in trying to fix this locally > when upstream zlib will be changing it in the near(?) future. He committed to removing the K&R function declarations when C23 is finalised: https://github.com/madler/zlib/issues

Re: clang 15 and zlib

2022-12-28 Thread Todd C . Miller
OK millert@ as well. There is no point in trying to fix this locally when upstream zlib will be changing it in the near(?) future. - todd

Re: clang 15 and zlib

2022-12-28 Thread Theo Buehler
On Wed, Dec 28, 2022 at 07:48:29PM +0100, Jeremie Courreges-Anglas wrote: > > To build src cleanly with clang-15 you'd need the diff below. The > alternative would be to patch our three zlib copies and wait for > upstream to fix it. A more comfortable alternative is to just neuter > the warning.

clang 15 and zlib

2022-12-28 Thread Jeremie Courreges-Anglas
To build src cleanly with clang-15 you'd need the diff below. The alternative would be to patch our three zlib copies and wait for upstream to fix it. A more comfortable alternative is to just neuter the warning. -Wno-unknown-warning-option prevents llvm 13 from complaining that it doesn't kno