All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13166] python-rpi-gpio: does not work against aarch64, unintentional side-effect of gcc-10 patch
Date: Wed, 19 Aug 2020 22:20:16 +0000	[thread overview]
Message-ID: <bug-13166-163-MX6PayYZxL@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13166-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=13166

--- Comment #1 from Christian Stewart <christian@paral.in> ---
According to this, originally the submitter tried to disable the warning, but
that patch was rejected by the maintainers:


http://buildroot-busybox.2317881.n4.nabble.com/PATCH-1-1-package-python-rpi-gpio-fix-build-with-gcc-10-x-td261727.html

Then they submitted another with the more deep changes, I wonder, what was so
bad about disabling the compiler warning?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2020-08-19 22:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-19 22:12 [Buildroot] [Bug 13166] New: python-rpi-gpio: does not work against aarch64, unintentional side-effect of gcc-10 patch bugzilla at busybox.net
2020-08-19 22:20 ` bugzilla at busybox.net [this message]
2020-08-19 22:31 ` [Buildroot] [Bug 13166] " bugzilla at busybox.net
2020-08-19 22:32 ` bugzilla at busybox.net
2020-08-20 21:09 ` bugzilla at busybox.net
2020-08-20 21:30 ` bugzilla at busybox.net
2020-08-20 22:24 ` bugzilla at busybox.net
2020-08-20 22:25 ` bugzilla at busybox.net
2020-08-20 23:33 ` bugzilla at busybox.net
2020-08-23 21:31 ` bugzilla at busybox.net

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=bug-13166-163-MX6PayYZxL@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.