Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Neuschäfer via buildroot" <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: "J. Neuschäfer" <j.neuschaefer@gmx.net>,
	"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/uclibc: fix missing m_tim issue
Date: Mon, 5 Aug 2024 01:20:18 +0200	[thread overview]
Message-ID: <ZrAMsplA7x-BAvrB@probook> (raw)
In-Reply-To: <Zq4PBulXFJ0Bcq9H@waldemar-brodkorb.de>

On Sat, Aug 03, 2024 at 01:05:42PM +0200, Waldemar Brodkorb wrote:
> Hi Thomas,
> Thomas Petazzoni wrote,
>
> > Hello Waldemar,
> >
> > On Sat, 3 Aug 2024 08:24:09 +0200
> > Waldemar Brodkorb <wbx@openadk.org> wrote:
> >
> > > Patch from upstream to fix missing m_tim issue.
> > >
> > > Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> > > ---
> > >  ...are-st_mtim-if-defined-__USE_XOPEN2K.patch | 205 ++++++++++++++++++
> > >  1 file changed, 205 insertions(+)
> > >  create mode 100644 package/uclibc/0003-bits-stat.h-Declare-st_mtim-if-defined-__USE_XOPEN2K.patch
> >
> > I believe this potentially fixes some autobuilder build issues. Do you
> > have some references to those build failures, perhaps?
>
> I actually do not remember the build failure.
> Was it tipidee?
>
> @J.: What was the autobuild failures you were getting w/o the patch?

tipidee, indeed. Here:

http://autobuild.buildroot.org/results/f07d6d6ae2331f9972974093c0503b9d3c6b914a/build-end.log

And someone else reported a similar issue with s6dns.


-- jn
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-08-04 23:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-03  6:24 [Buildroot] [PATCH] package/uclibc: fix missing m_tim issue Waldemar Brodkorb
2024-08-03  9:52 ` Thomas Petazzoni via buildroot
2024-08-03 11:05   ` Waldemar Brodkorb
2024-08-04 23:20     ` J. Neuschäfer via buildroot [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=ZrAMsplA7x-BAvrB@probook \
    --to=buildroot@buildroot.org \
    --cc=j.neuschaefer@gmx.net \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=wbx@openadk.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox