From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/libtirpc: fix build with gcc 10
Date: Thu, 5 Mar 2020 09:03:22 +0100 [thread overview]
Message-ID: <20200305090322.5b1e5fcc@windsurf> (raw)
In-Reply-To: <20200305043708.GA2841817@x230>
On Thu, 5 Mar 2020 05:37:08 +0100
Petr Vorel <petr.vorel@gmail.com> wrote:
> > This issue seems to be happening only on the next branch. Why? Anything
> > special in next compared to master?
> No idea why, libtirpc itself it's the same. It'd help if I could find builds for
> master, but autobuild search doesn't help to search packages, which does not
> fail, there is only search for failed packages:
>
> http://autobuild.buildroot.net/index.php?reason=libtirpc-1.2.5
>
> Is it running for master?
You can search the autobuilders for successful build results, filtering
per config options. See http://autobuild.buildroot.net/search.php.
For example:
http://autobuild.buildroot.net/index.php?status=OK&symbols%5BBR2_PACKAGE_LIBTIRPC%5D=y
will search all successful builds that had BR2_PACKAGE_LIBTIRPC enabled.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-03-05 8:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 17:30 [Buildroot] [PATCH 1/2] package/libtirpc: fix build with gcc 10 Petr Vorel
2020-02-28 17:30 ` [Buildroot] [PATCH 2/2] package/libtirpc: fix build when missing <bits/endian.h> Petr Vorel
2020-03-03 21:56 ` Thomas Petazzoni
2020-03-05 4:39 ` Petr Vorel
2020-03-23 18:24 ` Petr Vorel
2020-03-03 21:55 ` [Buildroot] [PATCH 1/2] package/libtirpc: fix build with gcc 10 Thomas Petazzoni
2020-03-05 4:37 ` Petr Vorel
2020-03-05 8:03 ` Thomas Petazzoni [this message]
2020-03-23 19:42 ` Petr Vorel
2020-03-24 7:20 ` Thomas Petazzoni
2020-03-05 4:44 ` Petr Vorel
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=20200305090322.5b1e5fcc@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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