Re: LZ4 enabled by default since 7c1849311e49
| От | Mark Wong |
|---|---|
| Тема | Re: LZ4 enabled by default since 7c1849311e49 |
| Дата | |
| Msg-id | abhpxc0fLdYTt3KP@ltdrgnflg2 обсуждение |
| Ответ на | Re: LZ4 enabled by default since 7c1849311e49 (Mark Wong <markwkm@gmail.com>) |
| Ответы |
Re: LZ4 enabled by default since 7c1849311e49
|
| Список | buildfarm-members |
On Thu, Mar 12, 2026 at 10:05:42AM -0700, Mark Wong wrote: > Hi everyone, > > On Wed, Mar 04, 2026 at 01:31:31PM +0900, Michael Paquier wrote: > > Hi all, > > (Added in CC buildfarm owners of animals that I know are already > > failing.) > > > > Since 7c1849311e49, LZ4 has been enabled by default in the builds on > > HEAD. Like ICU or readline, this can be overridden with the addition > > of a --without-lz4 to disable the library. If possible, I would > > recommend adding a package like lz4-devel or equivalent so as builds > > are able to work. > > > > Sorry for the inconvenience. > > I'm a little behind in catching up on email. Just wanted to say I'm > starting to get lz4 installed... Will keep you posted. I think have have most, if not all, animals with lz4 packages installed with lz4 now. (I've been trying to use Ansible to help, but there are still a number of systems Ansible isn't able to help me with.) What feels like the best way to continue at this point? Does having me update configs to set --with-lz4 make more sense than changing the default? Regards, Mark
В списке buildfarm-members по дате отправления: