From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Add TARGET_CFLAGS to efiemu link format test
Date: Mon, 27 Jan 2014 03:56:40 +0100 [thread overview]
Message-ID: <52E5CAE8.8090103@gmail.com> (raw)
In-Reply-To: <20140126162900.1b2c2b86@crass-Ideapad-Z570>
[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]
On 26.01.2014 23:29, Glenn Washburn wrote:
> Its been a while since I've compiled grub using the latest git. When I
> just did, the build now fails in configure when evaluating the efiemu
> link format test (which was being automatically chosen by efiemu
> option being guessed to "yes"). The proximate issue was that the test
> program failed to compile due to a missing include directory (which may
> be the result of a packaging issue on my machine).
>
> Whereas when compiling for the emu platform the efiemu allows for the
> CFLAGS to be affected by the TARGET_CFLAGS environment variable, there
> is no equivalent method to affect the CFLAGS of the test for i386
> platforms. So I added TARGET_CFLAGS (and TARGET_LDFLAGS) for symmetry
> with the emu platform.
>
> The attached patch allowed me to successfully compile with efiemu
> (untested since I don't actually use efiemu). Perhaps it will be of
> use to others.
>
efiemu is compiled in its own environment and using TARGET_CFLAGS on it
would break it in some cases. Please attach the logs of failed attempts.
> Glenn
>
>
>
> _______________________________________________
> 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: 274 bytes --]
prev parent reply other threads:[~2014-01-27 2:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-26 22:29 Add TARGET_CFLAGS to efiemu link format test Glenn Washburn
2014-01-27 2:56 ` Vladimir 'φ-coder/phcoder' Serbinenko [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=52E5CAE8.8090103@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 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.