From: Segher Boessenkool <segher@kernel.crashing.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: Don't use HOSTCFLAGS in BOOTCFLAGS
Date: Tue, 29 May 2007 08:26:49 +0200 [thread overview]
Message-ID: <5dbbc18a80b465a00d6bbb764c06af86@kernel.crashing.org> (raw)
In-Reply-To: <20070529053445.GD30266@localhost.localdomain>
>> Also, is there any reason why you can't simply use $(CC) -m32 with
>> the kernel $(CFLAGS) ?
>
> I did think about that. But the kernel CFLAGS does includes
> -ffixed-r2 and -Iarch/powerpc which I don't think we want here.
Both of these should be fairly harmless. But sure, it
is cleaner to have separate flags -- the booter and the
kernel run in different environments, after all.
Segher
next prev parent reply other threads:[~2007-05-29 6:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 3:29 Don't use HOSTCFLAGS in BOOTCFLAGS David Gibson
2007-05-29 5:12 ` Segher Boessenkool
2007-05-29 5:34 ` David Gibson
2007-05-29 6:26 ` Segher Boessenkool [this message]
2007-05-29 6:33 ` David Gibson
-- strict thread matches above, loose matches on Subject: below --
2007-05-29 5:37 David Gibson
2007-05-29 14:21 ` Josh Boyer
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=5dbbc18a80b465a00d6bbb764c06af86@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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.