From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/libtirpc: fix build when missing <bits/endian.h>
Date: Mon, 23 Mar 2020 19:24:43 +0100 [thread overview]
Message-ID: <20200323182443.GA3832536@x230> (raw)
In-Reply-To: <20200305043947.GA2842054@x230>
Hi Thomas,
> > This issue seems to be happening only on the next branch. Why? Anything
> > special in next compared to master?
Now, the error got propagated to the master, it'll fix failures on riscv64 and
arm:
http://autobuild.buildroot.net/results/4f423c95e290ec99fec263a839e3336362e7003c
http://autobuild.buildroot.net/results/04fdf097b9aeda2e831c9138110b527e1e6ee5ea
http://autobuild.buildroot.net/results/531156fd470eeb287e1761c5f0c17c68fe1e7888
http://autobuild.buildroot.net/results/678cd9b11160e3995e61afc8579b579702429ef5
http://autobuild.buildroot.net/results/940e4212a7d029e6495af3d5cacc8e3bbc9e78ff
You can merge it with previous one (gcc-10 fix [1]), or I can sent v2 with just
this patch (then I'd rename patch number from 6 to 5).
Kind regards,
Petr
[1] https://patchwork.ozlabs.org/patch/1246746/
next prev parent reply other threads:[~2020-03-23 18:24 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 [this message]
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
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=20200323182443.GA3832536@x230 \
--to=petr.vorel@gmail.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