From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: __stack_chk_fail in regexp is not defined
Date: Sun, 10 Nov 2013 14:35:00 +0100 [thread overview]
Message-ID: <527F8B84.3060203@gmail.com> (raw)
In-Reply-To: <20131110170234.3c46b23c@opensuse.site>
[-- Attachment #1: Type: text/plain, Size: 944 bytes --]
On 10.11.2013 14:02, Andrey Borzenkov wrote:
> В 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.
>
in "-m32 -m64" the last one takes precedence. But I'll adjust the test
to be nearer to truth.
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]
next prev parent reply other threads:[~2013-11-10 13:35 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
2013-11-10 13:35 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
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=527F8B84.3060203@gmail.com \
--to=phcoder@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).