From: Manuel Lauss <manuel.lauss@googlemail.com>
To: Manuel Lauss <manuel.lauss@googlemail.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Linux-MIPS <linux-mips@linux-mips.org>,
Dmitri Vorobiev <dmitri.vorobiev@gmail.com>
Subject: Re: MIPS: Alchemy build broken in latest linus-git [with patch]
Date: Thu, 24 Sep 2009 14:09:45 +0200 [thread overview]
Message-ID: <4ABB6189.5010909@gmail.com> (raw)
In-Reply-To: <f861ec6f0909240241x5c5858d4g4d44b40107021bb6@mail.gmail.com>
Manuel Lauss wrote:
> On Thu, Sep 24, 2009 at 11:24 AM, Manuel Lauss
> <manuel.lauss@googlemail.com> wrote:
>>> I'm away from my machine atm.
>>> Could you try to add the following to arch/mips/kernel/makefile:
>>>
>>> CPPFFLAGS_vmlinux.lds += $(KBUILD_CFLAGS)
>>>
>>> This should fix it.
>> Thank you, that did it.
>
> Spoke too soon:
>
> This leaves unprocessed directives in vmlinux.lds:
>
> [...]
> OUTPUT_ARCH(mips)
> ENTRY(kernel_entry)
> PHDRS {
> text PT_LOAD FLAGS(7); /* RWX */
> note PT_NOTE FLAGS(4); /* R__ */
> }
> ifdef 1
> ifdef 1
> jiffies = jiffies_64;
> else
> jiffies = jiffies_64 + 4;
> endif
> else
> jiffies = jiffies_6
... which is of course easily fixed after consumption of
unhealthy amounts of coffee.
Patch below works for me.
Thank you Sam!
Manuel Lauss
---
From: Manuel Lauss <manuel.lauss@gmail.com>
Subject: [PATCH] MIPS: fix build of vmlinux.lds
Commit 51b563fc93c8cb5bff1d67a0a71c374e4a4ea049 removed a few
CPPFLAGS with vital include paths necessary to build vmlinux.lds
on MIPS, and moved the calculation of the 'jiffies' symbol
directly to vmlinux.lds.S but forgot to change make ifdef/... to
cpp macros.
Signed-off-by: Manuel Lauss <manuel.lauss@gmail.com>
---
arch/mips/kernel/Makefile | 2 ++
arch/mips/kernel/vmlinux.lds.S | 12 ++++++------
2 files changed, 8 insertions(+), 6 deletions(-)
diff --git a/arch/mips/kernel/Makefile b/arch/mips/kernel/Makefile
index e961221..8e26e9c 100644
--- a/arch/mips/kernel/Makefile
+++ b/arch/mips/kernel/Makefile
@@ -91,3 +91,5 @@ CFLAGS_cpu-bugs64.o = $(shell if $(CC) $(KBUILD_CFLAGS) -Wa,-mdaddi -c -o /dev/n
obj-$(CONFIG_HAVE_STD_PC_SERIAL_PORT) += 8250-platform.o
EXTRA_CFLAGS += -Werror
+
+CPPFLAGS_vmlinux.lds := $(KBUILD_CFLAGS)
diff --git a/arch/mips/kernel/vmlinux.lds.S b/arch/mips/kernel/vmlinux.lds.S
index 9bf0e3d..162b299 100644
--- a/arch/mips/kernel/vmlinux.lds.S
+++ b/arch/mips/kernel/vmlinux.lds.S
@@ -11,15 +11,15 @@ PHDRS {
note PT_NOTE FLAGS(4); /* R__ */
}
-ifdef CONFIG_32BIT
- ifdef CONFIG_CPU_LITTLE_ENDIAN
+#ifdef CONFIG_32BIT
+ #ifdef CONFIG_CPU_LITTLE_ENDIAN
jiffies = jiffies_64;
- else
+ #else
jiffies = jiffies_64 + 4;
- endif
-else
+ #endif
+#else
jiffies = jiffies_64;
-endif
+#endif
SECTIONS
{
--
1.6.5.rc1
next prev parent reply other threads:[~2009-09-24 12:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 6:44 MIPS: Alchemy build broken in latest linus-git Manuel Lauss
2009-09-24 7:49 ` Dmitri Vorobiev
2009-09-24 9:15 ` Sam Ravnborg
2009-09-24 9:24 ` Manuel Lauss
2009-09-24 9:41 ` Manuel Lauss
2009-09-24 12:09 ` Manuel Lauss [this message]
2009-09-24 12:23 ` MIPS: Alchemy build broken in latest linus-git [with patch] Dmitri Vorobiev
2009-09-24 19:43 ` Sam Ravnborg
2009-09-25 8:48 ` Dmitri Vorobiev
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=4ABB6189.5010909@gmail.com \
--to=manuel.lauss@googlemail.com \
--cc=dmitri.vorobiev@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=sam@ravnborg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).