From: Adrian Bunk <bunk@stusta.de>
To: Armin Kuster <akuster808@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [zeus 26/29] valgrind: Fix build with -fno-common
Date: Sun, 5 Jan 2020 13:21:02 +0200 [thread overview]
Message-ID: <20200105112102.GF26925@localhost> (raw)
In-Reply-To: <8a25a3ecc4a4220c996ab91fb986598de7d1e917.1578155074.git.akuster808@gmail.com>
-fno-common is a changed default in the upcoming gcc 10,
this patch isn't needed in zeus.
cu
Adrian
next prev parent reply other threads:[~2020-01-05 11:21 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 16:25 [zeus 00/29] Patch review Armin Kuster
2020-01-04 16:25 ` [zeus 01/29] sstate: Add ability to hide summary output for sstate Armin Kuster
2020-01-04 16:25 ` [zeus 02/29] sstate: Stop overwriting SSTATE_PKG Armin Kuster
2020-01-04 16:25 ` [zeus 03/29] sstate: Ensure SSTATE_PKG is reloaded when handling siginfo Armin Kuster
2020-01-04 16:25 ` [zeus 04/29] sstate: Ensure target sstate directory exists if unihash changes Armin Kuster
2020-01-04 16:25 ` [zeus 05/29] sstate: Ensure mkdir happens before mktemp Armin Kuster
2020-01-04 16:25 ` [zeus 06/29] sstate.bbclass: Fix for consistent whitespace Armin Kuster
2020-01-04 16:25 ` [zeus 07/29] linux-yocto/5.2: update to v5.2.21 Armin Kuster
2020-01-04 16:25 ` [zeus 08/29] linux-yocto/5.2: update to v5.2.22 Armin Kuster
2020-01-04 16:25 ` [zeus 09/29] linux-yocto/5.2: update to v5.2.23 Armin Kuster
2020-01-04 16:25 ` [zeus 10/29] linux-yocto/4.19: update to v4.19.84 Armin Kuster
2020-01-04 16:25 ` [zeus 11/29] linux-yocto/5.2: update to v5.2.24 Armin Kuster
2020-01-04 16:25 ` [zeus 12/29] linux-yocto/4.19: update to v4.19.87 Armin Kuster
2020-01-04 16:25 ` [zeus 13/29] linux-yocto/5.2: update to v5.2.25 Armin Kuster
2020-01-04 16:25 ` [zeus 14/29] linux-yocto/5.2: update to v5.2.26 Armin Kuster
2020-01-04 16:25 ` [zeus 15/29] linux-yocto/5.2: update to v5.2.27 Armin Kuster
2020-01-04 16:25 ` [zeus 16/29] linux-yocto/4.19/5.2/-dev: fix gcc10 build Armin Kuster
2020-01-04 16:25 ` [zeus 17/29] linux-yocto/5.2: update to v5.2.28 Armin Kuster
2020-01-04 16:25 ` [zeus 18/29] liberror-perl: update 0.17027 -> 0.17028 Armin Kuster
2020-01-04 16:26 ` [zeus 19/29] podfix: class to remove Pod::Man versions from manpages Armin Kuster
2020-01-04 16:26 ` [zeus 20/29] reproducible_build_simple: inherit podfix Armin Kuster
2020-01-04 16:26 ` [zeus 21/29] podfix: only alter normal files Armin Kuster
2020-01-04 16:26 ` [zeus 22/29] systemd: Upgrade 243 -> 243.2 Armin Kuster
2020-01-04 16:26 ` [zeus 23/29] python3: Upgrade 3.7.5 -> 3.7.6 Armin Kuster
2020-01-04 16:26 ` [zeus 24/29] python3: RDEPEND on libgcc Armin Kuster
2020-01-04 16:26 ` [zeus 25/29] python3: Update to apply libgcc fix to libpython, glibc only Armin Kuster
2020-01-04 16:26 ` [zeus 26/29] valgrind: Fix build with -fno-common Armin Kuster
2020-01-05 11:21 ` Adrian Bunk [this message]
2020-01-07 20:43 ` akuster808
2020-01-04 16:26 ` [zeus 27/29] pseudo: Make realpath() remove trailing slashes Armin Kuster
2020-01-04 16:26 ` [zeus 28/29] libsdl2: fix failure appeared in bitbake libsdl2-native Armin Kuster
2020-01-04 16:26 ` [zeus 29/29] kernel: Make symbol link to vmlinux.64 in boot directory Armin Kuster
2020-01-06 10:59 ` [zeus 00/29] Patch review Manjukumar Harthikote Matha
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=20200105112102.GF26925@localhost \
--to=bunk@stusta.de \
--cc=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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