mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Markus Wichmann <nullplan@gmx.net>
To: musl@lists.openwall.com
Subject: Re: [musl] Revisiting LFS64 removal
Date: Fri, 30 Sep 2022 04:44:47 +0200	[thread overview]
Message-ID: <20220930024447.GC2645@voyager> (raw)
In-Reply-To: <20220929230707.GA29905@brightrain.aerifal.cx>

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

  reply	other threads:[~2022-09-30  2:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-26  1:03 Rich Felker
2022-09-26 16:03 ` Markus Wichmann
2022-09-26 16:47   ` Rich Felker
2022-09-26 22:04 ` Rich Felker
2022-09-27  9:09   ` Gabriel Ravier
2022-09-27 12:20     ` Rich Felker
2022-09-27 19:03       ` Rich Felker
2022-09-27 19:08         ` Rich Felker
2022-09-29 23:07           ` Rich Felker
2022-09-30  2:44             ` Markus Wichmann [this message]
2022-09-30 12:57               ` Rich Felker
2022-09-30 17:35                 ` Colin Cross
2022-09-30 18:13                   ` enh
2022-09-30 19:26                     ` Rich Felker
2022-09-30 23:03                       ` enh
2022-09-30 19:29                   ` Rich Felker
2022-09-30 19:41                     ` Rich Felker

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=20220930024447.GC2645@voyager \
    --to=nullplan@gmx.net \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).