All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Ho" <Michael.Ho@bmw.de>
To: openembedded-core@lists.openembedded.org
Subject: Re: Question about security_flags.inc and CC_ARCH
Date: Mon, 25 Jan 2021 08:57:49 -0800	[thread overview]
Message-ID: <5141.1611593869692038191@lists.openembedded.org> (raw)
In-Reply-To: <CAMKF1sp-tFGr12OBL+J0d4-Ykf7es5JJoY-eeicLJkGP0UHEfA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 637 bytes --]

Hi,

Thanks for the info/comments. It's clear that it wouldn't be wise to differ the SDK compiler flags from the bitbake flags.

Maybe coming back to the original point, what would the recommended way be for developers in an SDK to create debug builds of their software? Should they attempt to filter out FORTIFY_SOURCE from the compiler flags on their own?

Could it make sense to leave things like the stack-protector flags in CC_ARCH but move just FORTIFY_SOURCE to CFLAGS as FORTIFY_SOURCE does not do anything without optimisations (which should not be part of CC/CXX)?

Thanks for any advice!

Kind regards,
Michael Ho

[-- Attachment #2: Type: text/html, Size: 681 bytes --]

      reply	other threads:[~2021-01-25 16:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15 13:46 Question about security_flags.inc and CC_ARCH Michael Ho
2021-01-15 16:05 ` [OE-core] " Richard Purdie
2021-01-15 16:43   ` Joshua Watt
2021-01-15 20:35   ` Khem Raj
2021-01-25 16:57     ` Michael Ho [this message]

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=5141.1611593869692038191@lists.openembedded.org \
    --to=michael.ho@bmw.de \
    --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 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.