From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/libtirpc: fix build with gcc 10
Date: Thu, 5 Mar 2020 05:44:23 +0100 [thread overview]
Message-ID: <20200305044423.GA2842685@x230> (raw)
In-Reply-To: <20200228173052.5128-1-petr.vorel@gmail.com>
Hi Thomas,
sorry, previous reply was for the second patch.
> Is this for master or next ? Are you talking about gcc 10 for the host
> or gcc 10 for the target ?
I experienced this just when for native build on other distro (this patch was
needed for openSUSE), send with a hope it's useful. But feel free to drop it,
libtirpc is releasing often, now it's libtirpc-1-2-6-rc2. As nobody complains
about it, it can wait till the package release.
Kind regards,
Petr
prev parent reply other threads:[~2020-03-05 4:44 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
2020-03-23 19:42 ` Petr Vorel
2020-03-24 7:20 ` Thomas Petazzoni
2020-03-05 4:44 ` Petr Vorel [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=20200305044423.GA2842685@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