From: Khalid Aziz <khalid.aziz@hp.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: joeyli <jlee@suse.com>,
linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org
Subject: Re: Fwd: UEFI Secure boot using qemu-kvm
Date: Thu, 19 Jul 2012 09:55:36 -0600 [thread overview]
Message-ID: <1342713336.13917.124.camel@lyra> (raw)
In-Reply-To: <1342690897.3059.24.camel@dabdike.int.hansenpartnership.com>
On Thu, 2012-07-19 at 10:41 +0100, James Bottomley wrote:
> Actually, I just ran into this too. Apparently libefi.a needs to be
> build with -fno-stack-protector ... at least that's where the problem is
> coming from in my environment. I don't have an ubuntu system to check,
> but to verify this is your issue, try:
>
> nm -D /usr/lib/libefi.a | grep __stack_chk_fail
>
> (or whatever your path is to libefi.a) ... probably you should also
> check libgnuefi.a, although this one is clear in my setup.
On Ubuntu, it is coming from lib/lib.a. It so happens that "make clean"
does not descend into lib/ and remove *.o and lib.a. So, I added
"-fno-stack-protector" to top level Makefile, ran "make clean" followed
by make and it didn't help because I continuesd to use the old lib.a.
Now that I have realized it, I added "(cd lib; rm -f *.o lib.a)" to the
clean target in toplevel Makefile and ran a "make clean". After this
lib/Makefile inherited -fno-stack-protector in CFLAGS from Make.rules
and everything builds correctly now.
--
Khalid Aziz <khalid.aziz@hp.com>
prev parent reply other threads:[~2012-07-19 15:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 10:01 UEFI Secure boot using qemu-kvm joeyli
2012-06-28 10:22 ` James Bottomley
2012-06-28 10:49 ` joeyli
[not found] ` <CAGLnvc-hLpUZaaOkeWMRtYefwL5goxuWP_99FyAzem7s_mncPg@mail.gmail.com>
2012-06-28 10:24 ` Fwd: " joeyli
2012-06-30 16:21 ` joeyli
2012-07-12 22:17 ` Khalid Aziz
2012-07-19 9:41 ` James Bottomley
2012-07-19 15:55 ` Khalid Aziz [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=1342713336.13917.124.camel@lyra \
--to=khalid.aziz@hp.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jlee@suse.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@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 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.