From: Sam Ravnborg <sam@ravnborg.org>
To: sparclinux@vger.kernel.org
Subject: Re: [GIT PULL] unify sparc header files
Date: Mon, 07 Jul 2008 20:54:31 +0000 [thread overview]
Message-ID: <20080707205431.GA23647@uranus.ravnborg.org> (raw)
In-Reply-To: <20080628220235.GA3169@uranus.ravnborg.org>
On Mon, Jul 07, 2008 at 12:54:40AM -0700, David Miller wrote:
> From: Sam Ravnborg <sam@ravnborg.org>
> Date: Mon, 7 Jul 2008 09:46:00 +0200
>
> > # disable pointer signed / unsigned warnings in gcc 4.0
> > KBUILD_CFLAGS += $(call cc-option,-Wno-pointer-sign,)
> >
> > When we do the above check we use KBUILD_CFLAGS direct
> > and does not include KBUILD_CPPFLAGS - thus missing -m64.
> >
> > So I think that your bi-arch sparc gcc only accepts
> > -Wno-pointer-sign if -m64 is specified and that this
> > option is missing with current patchset.
> > At least that is my best explanation so far.
>
> Yep, that the source of the problem.
>
> What is happening is that the other sparc64 KBUILD_CFLAGS (such as
> -mcmodel=medlow, etc.) are only legal during a 64-bit compile. When
> compiling 32-bit those options are not allowed.
So I once again updated the patchset - they can be pulled here:
ssh://master.kernel.org/pub/scm/linux/kernel/git/sam/sparc2.git master
The only change is the replacement of the patch adding -m64.
The new commit is appended.
Diffstat and shortlog omitted - they did not change except for appended patch.
I have checked that:
1) We pass -m64 to gcc when building vmlinux.lds
2) that a defconfig builds here
3) that we continue to pass -m64 to gcc
Sam
commit bab6038071f446e2e6d57eb83028b21959276e84
Author: Sam Ravnborg <sam@ravnborg.org>
Date: Mon Jul 7 22:30:35 2008 +0200
sparc: add -m64 when building vmlinux.lds
David Miller noticed that the build of vmlinux.lds
failed to use the -m64 specifier.
This caused the build to break with a bi-arch gcc with
unified headers.
Add the -m64 option to CPPFLAGS_vmlinux.lds so we
have the correct defines available when building
vmliux.lds.
Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
diff --git a/arch/sparc64/Makefile b/arch/sparc64/Makefile
index 4b8f2b0..b785a39 100644
--- a/arch/sparc64/Makefile
+++ b/arch/sparc64/Makefile
@@ -9,7 +9,9 @@
CHECKFLAGS += -D__sparc__ -D__sparc_v9__ -m64
-CPPFLAGS_vmlinux.lds += -Usparc
+# Undefine sparc when processing vmlinux.lds - it is used
+# And teach CPP we are doing 64 bit builds (for this case)
+CPPFLAGS_vmlinux.lds += -m64 -Usparc
LDFLAGS := -m elf64_sparc
next prev parent reply other threads:[~2008-07-07 20:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-28 22:02 [GIT PULL] unify sparc header files Sam Ravnborg
2008-06-28 22:29 ` Sam Ravnborg
2008-06-29 6:27 ` Sam Ravnborg
2008-06-30 19:49 ` Adrian Bunk
2008-07-03 7:50 ` David Miller
2008-07-03 8:12 ` David Miller
2008-07-03 10:01 ` David Miller
2008-07-03 13:45 ` Sam Ravnborg
2008-07-03 20:02 ` Adrian Bunk
2008-07-03 20:15 ` David Miller
2008-07-03 20:29 ` Sam Ravnborg
2008-07-03 20:29 ` Sam Ravnborg
2008-07-04 21:10 ` Sam Ravnborg
2008-07-05 20:55 ` Sam Ravnborg
2008-07-05 23:03 ` Sam Ravnborg
2008-07-06 1:56 ` David Miller
2008-07-06 1:57 ` David Miller
2008-07-06 20:06 ` Sam Ravnborg
2008-07-07 1:18 ` David Miller
2008-07-07 7:46 ` Sam Ravnborg
2008-07-07 7:54 ` David Miller
2008-07-07 20:54 ` Sam Ravnborg [this message]
2008-07-08 9:33 ` David Miller
2008-07-09 4:27 ` Sam Ravnborg
2008-07-15 5:58 ` David Miller
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=20080707205431.GA23647@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=sparclinux@vger.kernel.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.