From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: buildroot@buildroot.org, Chin Huat Ang <chinhuat@gmail.com>
Subject: Re: [Buildroot] [PATCH] package/uclibc: bump to version 1.0.47, add Y2038 config option
Date: Sun, 7 Apr 2024 23:11:46 +0200 [thread overview]
Message-ID: <20240407231146.0b9fcf12@windsurf> (raw)
In-Reply-To: <6e119079-bbae-49dd-b3f7-f8117e8a201e@mind.be>
On Sun, 7 Apr 2024 21:30:09 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:
> IMHO the question is if uClibc acts like musl (i.e. unconditionally enable
> 64-bit time, which breaks binaries that were compiled with 32-bit time) or like
> glibc (i.e. the compiled library supports both 32-bit and 64-bit time, and
> applications use the one or other version depending on _TIME_BITS).
>
> I _think_ that uClibc acts like musl. In that case, passing -D_TIME_BITS=64
> doesn't make any sense. And therefore, having the option at uClibc level makes
> more sense. However, I don't think it's very useful to have this configuration
> knob in Buildroot's config. What I would do instead is to unconditionally change
> our bundled uClibc config to enable 64-bit time, and let people provide their
> own config if for some reason they don't want 64-bit time.
If we go this way, then we should also do it for glibc, and drop
BR2_TIME_BITS_64.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-04-07 21:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-06 15:43 [Buildroot] [PATCH] package/uclibc: bump to version 1.0.47, add Y2038 config option Chin Huat Ang
2024-04-06 21:37 ` Thomas Petazzoni via buildroot
2024-04-07 17:47 ` Chin Huat Ang
2024-04-07 19:30 ` Arnout Vandecappelle via buildroot
2024-04-07 21:11 ` Thomas Petazzoni via buildroot [this message]
2024-04-09 12:23 ` Arnout Vandecappelle via buildroot
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=20240407231146.0b9fcf12@windsurf \
--to=buildroot@buildroot.org \
--cc=arnout@mind.be \
--cc=chinhuat@gmail.com \
--cc=thomas.petazzoni@bootlin.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.