From: Andrey Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: __stack_chk_fail in regexp is not defined
Date: Sun, 10 Nov 2013 17:02:34 +0400 [thread overview]
Message-ID: <20131110170234.3c46b23c@opensuse.site> (raw)
In-Reply-To: <527F79A1.1000405@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 600 bytes --]
В Sun, 10 Nov 2013 13:18:41 +0100
Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com> пишет:
> Fixed, thanks for spotting those tests.
if test x"$efiemu_excuse" = x ; then
AC_CACHE_CHECK([whether options required for efiemu work], grub_cv_cc_efiemu,
[
- CFLAGS="$TARGET_CFLAGS -m64 -mcmodel=large -mno-red-zone -nostdlib"
+ CFLAGS="$TARGET_CFLAGS -march=core2 -m64 -mcmodel=large -mno-red-zone -nost
dlib"
That's still wrong. efiemuXX.o does not use TARGET_CFLAGS, this test
will always fail on x86 because at this point TARGET_CFLAGS contains
-m32 already.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-11-10 13:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 18:42 __stack_chk_fail in regexp is not defined Glenn Washburn
2013-11-08 18:54 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-08 20:42 ` Glenn Washburn
2013-11-09 4:11 ` Andrey Borzenkov
2013-11-09 11:37 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-10 5:09 ` Glenn Washburn
2013-11-10 5:39 ` Andrey Borzenkov
2013-11-10 5:53 ` Andrey Borzenkov
2013-11-10 7:24 ` Andrey Borzenkov
2013-11-10 7:35 ` Andrey Borzenkov
2013-11-10 12:18 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-10 13:02 ` Andrey Borzenkov [this message]
2013-11-10 13:35 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-10 5:33 ` Glenn Washburn
2013-11-10 5:40 ` Andrey Borzenkov
2013-11-10 8:11 ` Glenn Washburn
2013-11-08 18:56 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=20131110170234.3c46b23c@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.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).