Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Leonid Yuriev <leo@yuriev.ru>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [autobuild.buildroot.net] Your daily results for 2022-11-30
Date: Thu, 1 Dec 2022 16:51:50 +0100	[thread overview]
Message-ID: <20221201165150.4746c32e@windsurf> (raw)
In-Reply-To: <3b7ef091-b01c-59d3-d31b-8b28e59bf1df@yuriev.ru>

Hello Leonid,

Thanks for your feedback. Could you provide more specific, such as
which specific version bump fixed this issue?

Best regards,

Thomas Petazzoni

On Thu, 1 Dec 2022 18:37:02 +0300
Leonid Yuriev <leo@yuriev.ru> wrote:

> Hi,
> 
> Just in case, I decided to notify that the problem has been fixed in the 
> latest version.
> I.e. it is enough to backport a libmdbx' package patches from the master 
> branch.
> 
> Regards,
> Leonid.
> 
> 01.12.2022 10:43, Thomas Petazzoni пишет:
> > Hello,
> >
> > Autobuilder failures
> > ====================
> >
> > Below is a list of build failures reported by the Buildroot autobuilders
> > in relation to packages or CPU architectures you are in charge of.
> > Please help us improving the quality of Buildroot by investigating those
> > build failures and sending patches to fix them.
> >
> > Results for the 'master' branch
> > -------------------------------
> >
> > Build failures related to your packages:
> >
> >      arch     |             reason             |                                       url
> > -------------+--------------------------------+---------------------------------------------------------------------------------
> >   microblaze  |        libmdbx-0.11.12         | http://autobuild.buildroot.net/results/06d9f3c5ad6a4415685dea6c5fb2f7aed910aa6e
> >
> >
> > Thanks for your contribution to Buildroot!
> >  



-- 
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

       reply	other threads:[~2022-12-01 15:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221201104313.25K7I8a6@myt5-1a3effcffc39.qloud-c.yandex.net>
     [not found] ` <3b7ef091-b01c-59d3-d31b-8b28e59bf1df@yuriev.ru>
2022-12-01 15:51   ` Thomas Petazzoni via buildroot [this message]
     [not found]     ` <a89a5a97-317a-b634-65ad-5fa11e526bc0@yuriev.ru>
2022-12-01 16:41       ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2022-11-30 Thomas Petazzoni via buildroot
2022-12-01 20:59         ` Peter Korsgaard
2022-12-01 21:08           ` Leonid Yuriev
2022-12-01 21:22             ` Peter Korsgaard

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=20221201165150.4746c32e@windsurf \
    --to=buildroot@buildroot.org \
    --cc=leo@yuriev.ru \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox