Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220930024447.GC2645@voyager>
Date: Fri, 30 Sep 2022 04:44:47 +0200
From: Markus Wichmann <nullplan@....net>
To: musl@...ts.openwall.com
Subject: Re: Revisiting LFS64 removal

On Thu, Sep 29, 2022 at 07:07:08PM -0400, Rich Felker wrote:
> As an alternative, maybe we should consider leaving these but only
> under explict _LARGEFILE64_SOURCE rather than implicitly via
> _GNU_SOURCE for at least one release cycle. This would allow makeshift
> fixing of any builds that break by just adding -D_LARGEFILE64_SOURCE
> until a proper fix can be applied.
>
> Any preference here?
>
> Rich

Given that nothing lasts as long as a temporary measure, I'd say it is
better to rip the band-aid off in one go rather than two. Besides, any
breakage ought to be able to be dealt with by a simple replacement,
right?

Ciao,
Markus

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.