From: Ondrej Mosnacek <omosnace@redhat.com>
To: selinux@vger.kernel.org
Subject: [PATCH userspace v2 0/4] Fix build with -fno-common
Date: Thu, 23 Jan 2020 13:57:12 +0100 [thread overview]
Message-ID: <20200123125716.12662-1-omosnace@redhat.com> (raw)
GCC 10 is going to enable -fno-common by default [1], so fix all build
errors uncovered by it and add it to global CFLAGS to avoid introducing
new bugs.
Changes in v2:
- remove also struct te_assert definition, which is also useless
- redo cil_mem_error_handler to match commit 4459d635b8f1 as suggested
by Jim Carter
Travis build: [2]
[1] https://gcc.gnu.org/gcc-10/porting_to.html#common
[2] https://travis-ci.org/WOnder93/selinux/builds/640875119
Ondrej Mosnacek (4):
libsepol: fix CIL_KEY_* build errors with -fno-common
libsepol: remove leftovers of cil_mem_error_handler
checkpolicy: remove unused te_assertions
Makefile: always build with -fno-common
Makefile | 3 +-
checkpolicy/checkpolicy.h | 14 --
libsepol/cil/src/cil.c | 162 ++++++++++++++++
libsepol/cil/src/cil_internal.h | 322 ++++++++++++++++----------------
libsepol/cil/src/cil_mem.h | 1 -
libsepol/cil/src/cil_strpool.c | 8 +-
6 files changed, 329 insertions(+), 181 deletions(-)
--
2.24.1
next reply other threads:[~2020-01-23 12:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 12:57 Ondrej Mosnacek [this message]
2020-01-23 12:57 ` [PATCH userspace v2 1/4] libsepol: fix CIL_KEY_* build errors with -fno-common Ondrej Mosnacek
2020-01-23 12:57 ` [PATCH userspace v2 2/4] libsepol: remove leftovers of cil_mem_error_handler Ondrej Mosnacek
2020-01-23 12:57 ` [PATCH userspace v2 3/4] checkpolicy: remove unused te_assertions Ondrej Mosnacek
2020-01-23 12:57 ` [PATCH userspace v2 4/4] Makefile: always build with -fno-common Ondrej Mosnacek
2020-01-23 18:26 ` [Non-DoD Source] " jwcart2
2020-01-28 9:54 ` Petr Lautrbach
2020-01-24 10:39 ` [PATCH userspace v2 0/4] Fix " Jason Zaman
2020-01-24 11:15 ` Ondrej Mosnacek
2020-01-27 15:56 ` [Non-DoD Source] " jwcart2
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=20200123125716.12662-1-omosnace@redhat.com \
--to=omosnace@redhat.com \
--cc=selinux@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).