All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollis@penguinppc.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [patch] Fix for building correct code on i386-pc (CVS-HEAD)
Date: Tue, 30 May 2006 16:15:51 -0500	[thread overview]
Message-ID: <1149023752.7177.86.camel@basalt.austin.ibm.com> (raw)
In-Reply-To: <447CB449.9080901@nic.fi>

On Wed, 2006-05-31 at 00:08 +0300, Vesa Jääskeläinen wrote:
> Attached patch fixes problems for compiling correct code on i386-pc...
> other platforms needs to be modified similarly too...

I'm confused by this; could you explain? If _TARGET_CFLAGS is used for
everything to be run on the target, perhaps we should just rename
_CFLAGS to _TARGET_CFLAGS.

Also, in the future, could you please supply best-guess code for other
architectures? It's ok if you don't know, but in this case it seems it
would be easy enough to duplicate your i386-pc.mk changes for the
other .mk files.

> Index: conf/common.rmk
> ===================================================================
> RCS file: /sources/grub/grub2/conf/common.rmk,v
> retrieving revision 1.7
> diff -u -r1.7 common.rmk
> --- conf/common.rmk	27 May 2006 21:09:25 -0000	1.7
> +++ conf/common.rmk	30 May 2006 21:00:02 -0000
> @@ -27,61 +27,73 @@
>  # For fshelp.mod.
>  fshelp_mod_SOURCES = fs/fshelp.c
>  fshelp_mod_CFLAGS = $(COMMON_CFLAGS)
> +fshelp_mod_TARGET_CFLAGS = $(COMMON_TARGET_CFLAGS)
>  fshelp_mod_LDFLAGS = $(COMMON_LDFLAGS)

...

> --- conf/i386-pc.rmk	28 May 2006 23:01:43 -0000	1.65
> +++ conf/i386-pc.rmk	30 May 2006 21:00:02 -0000
> @@ -2,6 +2,7 @@
>  
>  COMMON_ASFLAGS = -nostdinc -fno-builtin
>  COMMON_CFLAGS = -fno-builtin -mrtd -mregparm=3 -m32
> +COMMON_TARGET_CFLAGS = -fno-builtin -mrtd -mregparm=3 -m32
>  COMMON_LDFLAGS = -melf_i386 -nostdlib





  reply	other threads:[~2006-05-30 21:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-30 21:08 [patch] Fix for building correct code on i386-pc (CVS-HEAD) Vesa Jääskeläinen
2006-05-30 21:15 ` Hollis Blanchard [this message]
2006-05-31  3:59   ` Harley D. Eades III
2006-05-30 22:00     ` Hollis Blanchard
2006-05-31  0:31       ` Yoshinori K. Okuji
2006-05-31 21:00         ` [PATCH] Fix for configure on x86_64 (Was: Re: [patch] Fix for building correct code on i386-pc (CVS-HEAD)) Jeroen Dekkers
2006-06-01 15:39           ` Yoshinori K. Okuji
2006-06-07 11:16             ` [PATCH] Another fix for x86_64 Jeroen Dekkers
2006-06-07 15:55               ` Marco Gerards
2006-05-30 22:10 ` [patch] Fix for building correct code on i386-pc (CVS-HEAD) Marco Gerards
2006-05-31  0:28 ` Yoshinori K. Okuji

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=1149023752.7177.86.camel@basalt.austin.ibm.com \
    --to=hollis@penguinppc.org \
    --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.