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: Thu, 20 Aug 2020 21:09:45 +0000 [thread overview]
Message-ID: <bug-13166-163-UuxWu1LgK3@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13166-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=13166
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yann.morin.1998 at free.fr
--- Comment #4 from Yann E. MORIN <yann.morin.1998@free.fr> ---
(In reply to Christian Stewart from comment #1)
> I wonder, what was so bad about disabling the compiler warning?
Because duplicate symbols are a source for bugs. If we just add the -fcommon
option, this indeed hides the warning away, but the problematic code will not
get fixed, and we will have to carry that option ad libitum.
Instead, we want patches that fixes those warnings, so those patches are sent
to the corresponding upstreams, so the packages get fixed, and so we can drop
those patches in a future version bump.
So, I've had a look a deeper look at the patch now, and indeed it is not
complete... I'll follow up with a revised fix. Stay tuned to the ML.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-08-20 21:09 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 ` [Buildroot] [Bug 13166] " bugzilla at busybox.net
2020-08-19 22:31 ` bugzilla at busybox.net
2020-08-19 22:32 ` bugzilla at busybox.net
2020-08-20 21:09 ` bugzilla at busybox.net [this message]
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-UuxWu1LgK3@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox