public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Leif Lindholm" <leif.lindholm@linaro.org>
To: "Ooi, Tzy Way" <tzy.way.ooi@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	Ard BieSheuvel <ard.biesheuvel@linaro.org>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	"Loh, Tien Hock" <tien.hock.loh@intel.com>
Subject: Re: [edk2-devel] [PATCH v6 edk2-platforms 1/1] Silicon/Synopsys/Designware/Driver: DwEmacSnpDxe: Add DesignWare EMAC driver
Date: Wed, 17 Jul 2019 12:44:08 +0100	[thread overview]
Message-ID: <20190717114408.GA2712@bivouac.eciton.net> (raw)
In-Reply-To: <5F1105621EDF844291AF8B109E27C06D34D2EC31@PGSMSX109.gar.corp.intel.com>

Hi Tzy Way,

On Wed, Jul 17, 2019 at 09:25:49AM +0000, Ooi, Tzy Way wrote:
> Ya. I am on Linux. I managed to replicated the warning that you have
> provided in the previous email thread by using the gcc 8.3.

Excellent.

> Currently,  I'm looking at the compiler warning/error. While I am
> fixing the issue when compiling the source code, I encountered
> another issue where the compiler complain "undefined reference to
> __stack_chk_fail". I check from google and it can be solved by
> setting -fnostack-protector. Hence, I would like to ask if is it ok
> to set this to the CFLAGs for the compiler?

We don't need that workaround - since we have a proper way of handling
it in MdePkg/Library/BaseStackCheckLib/BaseStackCheckLib.inf

Adding a NULL resolution to the appropriate [LibraryClasses] section
in the .dsc should resolve this for you.

See (for example) edk2/EmbeddedPkg/EmbeddedPkg.dsc for guidance.

Best Regards,

Leif

  reply	other threads:[~2019-07-17 11:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-08  7:05 [PATCH v6 edk2-platforms 1/1] Silicon/Synopsys/Designware/Driver: DwEmacSnpDxe: Add DesignWare EMAC driver Ooi, Tzy Way
2019-07-11 16:43 ` Leif Lindholm
2019-07-16  9:37   ` [edk2-devel] " Ooi, Tzy Way
2019-07-16 17:22     ` Leif Lindholm
2019-07-17  9:25       ` Ooi, Tzy Way
2019-07-17 11:44         ` Leif Lindholm [this message]
2019-07-19  6:41           ` Ooi, Tzy Way

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-list 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=20190717114408.GA2712@bivouac.eciton.net \
    --to=devel@edk2.groups.io \
    /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