From: Ondrej Mosnacek <omosnace@redhat.com>
To: selinux@vger.kernel.org
Subject: [PATCH userspace 0/4] Fix build with -fno-common
Date: Wed, 22 Jan 2020 16:46:51 +0100 [thread overview]
Message-ID: <20200122154655.257233-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.
Travis build: [2]
[1] https://gcc.gnu.org/gcc-10/porting_to.html#common
[2] https://travis-ci.org/WOnder93/selinux/builds/640506702
Ondrej Mosnacek (4):
libsepol: fix CIL_KEY_* build errors with -fno-common
libsepol: remove unused cil_mem_error_handler
checkpolicy: remove unused te_assertions
Makefile: always build with -fno-common
Makefile | 3 +-
checkpolicy/checkpolicy.h | 2 -
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 | 2 -
6 files changed, 325 insertions(+), 167 deletions(-)
--
2.24.1
next reply other threads:[~2020-01-22 15:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 15:46 Ondrej Mosnacek [this message]
2020-01-22 15:46 ` [PATCH userspace 1/4] libsepol: fix CIL_KEY_* build errors with -fno-common Ondrej Mosnacek
2020-01-22 15:46 ` [PATCH userspace 2/4] libsepol: remove unused cil_mem_error_handler Ondrej Mosnacek
2020-01-22 18:54 ` [Non-DoD Source] " jwcart2
2020-01-23 11:59 ` Ondrej Mosnacek
2020-01-22 15:46 ` [PATCH userspace 3/4] checkpolicy: remove unused te_assertions Ondrej Mosnacek
2020-01-22 16:10 ` Ondrej Mosnacek
2020-01-22 15:46 ` [PATCH userspace 4/4] Makefile: always build with -fno-common Ondrej Mosnacek
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=20200122154655.257233-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).