All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Roberts <bill.c.roberts@gmail.com>
To: Stephen Smalley <stephen.smalley.work@gmail.com>
Cc: Laurent Bigonville <bigon@debian.org>,
	Petr Lautrbach <plautrba@redhat.com>,
	SElinux list <selinux@vger.kernel.org>,
	William Roberts <william.c.roberts@intel.com>
Subject: Re: [PATCH v2] README: start a section for documenting CFLAGS
Date: Mon, 8 Jun 2020 17:34:20 -0500	[thread overview]
Message-ID: <CAFftDdpSDpCNNhgaCK63KUcuFys-qXzWVZCQcqnCBHEm1BHORA@mail.gmail.com> (raw)
In-Reply-To: <CAEjxPJ7AtH67Gdoj6eHGJ22mXWYHWOqaRZP+Gi18aR5iJeJ5Cg@mail.gmail.com>

On Mon, Jun 8, 2020 at 11:21 AM Stephen Smalley
<stephen.smalley.work@gmail.com> wrote:
>
> On Mon, Jun 8, 2020 at 11:37 AM <bill.c.roberts@gmail.com> wrote:
> >
> > From: William Roberts <william.c.roberts@intel.com>
> >
> > Start a section in the README for documenting that custom CFLAGS yields
> > CUSTOM results and that your mileage may vary. The first CFLAG to
> > document that you likely want to include is -fsemantic-interposition.
>
> CUSTOM is all-caps for some reason, and it should be

Meant to emphasize CUSTOM RESULTS, but it only really emphasizes
it correctly if RESULTS is also capitalized (which it wasn't).

> -fno-semantic-interposition.

Argh, I forgot to change that, sorry.

>
> > diff --git a/README.md b/README.md
> > index 9d64f0b5cf90..eb8e170ea1f7 100644
> > --- a/README.md
> > +++ b/README.md
> > +
> > +- -fsemantic-interposition for gcc or compilers that do not do this. clang does this by default. clang-10 and up
> > +   will support passing this flag, but ignore it. Previous clang versions fail.
>
> -fno-semantic-interposition

  reply	other threads:[~2020-06-08 22:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-23 10:56 CFLAGS overridden by distribution build system Laurent Bigonville
2020-05-23 15:59 ` William Roberts
2020-05-29 13:31   ` Stephen Smalley
2020-05-29 16:04     ` William Roberts
2020-05-29 16:40       ` Stephen Smalley
2020-05-29 17:15         ` William Roberts
2020-05-29 18:18           ` Stephen Smalley
2020-05-29 20:59             ` William Roberts
2020-06-01  9:34               ` Petr Lautrbach
2020-06-02 18:55                 ` [PATCH] README: start a section for documenting CFLAGS bill.c.roberts
2020-06-04 19:03                   ` Stephen Smalley
2020-06-08 15:37                     ` [PATCH v2] " bill.c.roberts
2020-06-08 16:21                       ` Stephen Smalley
2020-06-08 22:34                         ` William Roberts [this message]
2020-06-08 22:38                         ` [PATCH v3] " bill.c.roberts
2020-06-09 11:57                           ` Stephen Smalley

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=CAFftDdpSDpCNNhgaCK63KUcuFys-qXzWVZCQcqnCBHEm1BHORA@mail.gmail.com \
    --to=bill.c.roberts@gmail.com \
    --cc=bigon@debian.org \
    --cc=plautrba@redhat.com \
    --cc=selinux@vger.kernel.org \
    --cc=stephen.smalley.work@gmail.com \
    --cc=william.c.roberts@intel.com \
    /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.