All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [ppc patch] link with -m32
Date: Sat, 15 Apr 2006 12:36:14 +0200	[thread overview]
Message-ID: <87ejzzceht.fsf@xs4all.nl> (raw)
In-Reply-To: <1fa98bd274eb1d8fffb77fe4de3f1363@penguinppc.org> (Hollis Blanchard's message of "Sat, 15 Apr 2006 00:27:53 -0500")

Hollis Blanchard <hollis@penguinppc.org> writes:

> On Apr 14, 2006, at 11:06 PM, Hollis Blanchard wrote:
>
>> Some 64-bit PowerPC compilers default to 64-bit output. Right now
>> we're building all the object files with -m32, but then the linker
>> complains when it tries to link a 64-bit grubof. We need to add -m32
>> to LDFLAGS as well as CFLAGS.
>
> Hmm, I didn't notice the error messages this caused. -m32 is a gcc
> flag, not an ld flag. However, there's some confusion about LDFLAGS
> and CFLAGS in genmk.rb (and conf/*.rmk). In particular, you cannot do
> $(CC) $(LDFLAGS), and you cannot do $(LD) $(CFLAGS).
>
> There is also confusion about which *FLAGS are used to build which
> targets. I've been investigating, but in the meantime this patch won't
> work.

I think LDFLAGS are really processed by cc, no?  So we do not use ld,
but cc if I am not mistaken.

Can you show what you currently have?  Or should I just look at your
previous patch?

--
Marco




  reply	other threads:[~2006-04-15 10:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-15  4:06 [ppc patch] link with -m32 Hollis Blanchard
2006-04-15  5:27 ` Hollis Blanchard
2006-04-15 10:36   ` Marco Gerards [this message]
2006-04-15 12:44     ` Vincent Pelletier
2006-04-15 13:37     ` Hollis Blanchard
2006-04-15 13:54     ` Hollis Blanchard
2006-04-15 14:06       ` LDFLAGS Hollis Blanchard
2006-04-15 16:08         ` LDFLAGS 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=87ejzzceht.fsf@xs4all.nl \
    --to=mgerards@xs4all.nl \
    --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.