[U-Boot] [PATCH v3] Fixup native builds on powerpc
When we changed ARCH from ppc to powerpc we need to treat HOSTARCH the same way. We use HOSTARCH == ARCH to determine if a build is native.
Signed-off-by: Kumar Gala galak@kernel.crashing.org --- * Put the ppc64 case first otherwise we get powerpc64
Makefile | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/Makefile b/Makefile index 25e3b8c..f2b1ed9 100644 --- a/Makefile +++ b/Makefile @@ -38,9 +38,9 @@ HOSTARCH := $(shell uname -m | \ -e s/sun4u/sparc64/ \ -e s/arm.*/arm/ \ -e s/sa110/arm/ \ - -e s/powerpc/ppc/ \ - -e s/ppc64/ppc/ \ - -e s/macppc/ppc/) + -e s/ppc64/powerpc/ \ + -e s/ppc/powerpc/ \ + -e s/macppc/powerpc/)
HOSTOS := $(shell uname -s | tr '[:upper:]' '[:lower:]' | \ sed -e 's/(cygwin).*/cygwin/')
Dear Kumar Gala,
In message 1272441122-27976-1-git-send-email-galak@kernel.crashing.org you wrote:
When we changed ARCH from ppc to powerpc we need to treat HOSTARCH the same way. We use HOSTARCH == ARCH to determine if a build is native.
Signed-off-by: Kumar Gala galak@kernel.crashing.org
- Put the ppc64 case first otherwise we get powerpc64
Makefile | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-)
Undid v2, applied this one instead.
Kumar, could you please add proper In-reply-to:/References: headers to postings that obsolete earlier patches, so the new versions show up in the thread? Thanks.
Best regards,
Wolfgang Denk
On May 6, 2010, at 5:01 PM, Wolfgang Denk wrote:
Dear Kumar Gala,
In message 1272441122-27976-1-git-send-email-galak@kernel.crashing.org you wrote:
When we changed ARCH from ppc to powerpc we need to treat HOSTARCH the same way. We use HOSTARCH == ARCH to determine if a build is native.
Signed-off-by: Kumar Gala galak@kernel.crashing.org
- Put the ppc64 case first otherwise we get powerpc64
Makefile | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-)
Undid v2, applied this one instead.
Kumar, could you please add proper In-reply-to:/References: headers to postings that obsolete earlier patches, so the new versions show up in the thread? Thanks.
How do you do that with git send-email?
- k
Dear Kumar Gala,
In message BC53D917-2155-485A-9C71-7690EF51C1ED@kernel.crashing.org you wrote:
Kumar, could you please add proper In-reply-to:/References: headers to postings that obsolete earlier patches, so the new versions show up in the thread? Thanks.
How do you do that with git send-email?
Enter the message ID of the message you are referring to when git send-email asks for the "Message-ID to be used as In-Reply-To for the first email".
Best regards,
Wolfgang Denk
Hi Kumar,
Kumar, could you please add proper In-reply-to:/References: headers to postings that obsolete earlier patches, so the new versions show up in the thread? Thanks.
How do you do that with git send-email?
If called without --compose git send-email will prompt for such a reference:
$ git send-email --to u-boot@lists.denx.de 0001* Who should the emails appear to be from? [Detlev Zundel dzu@denx.de] Emails will be sent from: Detlev Zundel dzu@denx.de Message-ID to be used as In-Reply-To for the first email?
Reading the man page it should also be possible to use "--in-reply-to".
Cheers Detlev
On May 7, 2010, at 3:00 AM, Detlev Zundel wrote:
Hi Kumar,
Kumar, could you please add proper In-reply-to:/References: headers to postings that obsolete earlier patches, so the new versions show up in the thread? Thanks.
How do you do that with git send-email?
If called without --compose git send-email will prompt for such a reference:
$ git send-email --to u-boot@lists.denx.de 0001* Who should the emails appear to be from? [Detlev Zundel dzu@denx.de] Emails will be sent from: Detlev Zundel dzu@denx.de Message-ID to be used as In-Reply-To for the first email?
Reading the man page it should also be possible to use "--in-reply-to".
Cheers Detlev
Thanks guys.
- k
On May 6, 2010, at 5:01 PM, Wolfgang Denk wrote:
Dear Kumar Gala,
In message 1272441122-27976-1-git-send-email-galak@kernel.crashing.org you wrote:
When we changed ARCH from ppc to powerpc we need to treat HOSTARCH the same way. We use HOSTARCH == ARCH to determine if a build is native.
Signed-off-by: Kumar Gala galak@kernel.crashing.org
- Put the ppc64 case first otherwise we get powerpc64
Makefile | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-)
Undid v2, applied this one instead.
Should this be in your public git tree? Not seeing it.
- k
Dear Kumar Gala,
In message 09F91859-E41C-4C42-B1D4-93D428123F88@kernel.crashing.org you wrote:
Undid v2, applied this one instead.
Should this be in your public git tree? Not seeing it.
It should, but was not mirrored out yet. Now it is.
Best regards,
Wolfgang Denk
participants (3)
-
Detlev Zundel -
Kumar Gala -
Wolfgang Denk