All of lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Chin Huat Ang <chinhuat@gmail.com>,
	Dmitry Chestnykh <dm.chestnykh@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/uclibc: enable time64 support
Date: Mon, 15 Jul 2024 14:59:17 +0200	[thread overview]
Message-ID: <ZpUdJSlXXfp3T/bg@waldemar-brodkorb.de> (raw)
In-Reply-To: <20240715144514.56030468@windsurf>

Hi,
Thomas Petazzoni wrote,

> Hello Waldemar,
> 
> On Sun, 14 Apr 2024 09:36:18 +0200
> Waldemar Brodkorb <wbx@openadk.org> wrote:
> 
> > uClibc-ng supports time64 since release 1.0.46.
> > This commit enables it by default.
> > It was discussed on the mailinglist and one suggestion was to
> > enable it by default without a config option inside buildroot.
> > 
> > Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> > ---
> >  package/uclibc/uClibc-ng.config | 1 +
> >  1 file changed, 1 insertion(+)
> 
> My understanding is that since we've updated to 1.0.49, this is anyway
> the default, so this patch in fact isn't needed anymore, as we've
> already enabled 64-bit time_t on 32-bit archs with uClibc-ng since we
> bumped to 1.0.49. So I marked this patch as Rejected. Of course, let me
> know if I misunderstood the situation.

No, perfectly fine description of the situation.

best regards
 Waldemar
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-07-15 13:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-14  7:36 [Buildroot] [PATCH] package/uclibc: enable time64 support Waldemar Brodkorb
2024-07-15 12:45 ` Thomas Petazzoni via buildroot
2024-07-15 12:59   ` Waldemar Brodkorb [this message]

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=ZpUdJSlXXfp3T/bg@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --cc=buildroot@buildroot.org \
    --cc=chinhuat@gmail.com \
    --cc=dm.chestnykh@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.