All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Haavard Skinnemoen <hskinnemoen@atmel.com>,
	Paul Mundt <lethal@linux-sh.org>,
	linux-next@vger.kernel.org
Subject: Re: linux-next build poblems
Date: Mon, 23 Jun 2008 22:21:56 +0200	[thread overview]
Message-ID: <20080623202156.GA12027@uranus.ravnborg.org> (raw)
In-Reply-To: <20080623200702.GC8573@uranus.ravnborg.org>

> 
> I need to work out something.
> But my first attemps failed miserably and I will stop for now
> as I have some day-time job stuff to be done.
> Travelling for a few days from now one so I cannot do anything
> until the weekend.
I came up with the following fix.
And I fixed an arm tool chain for my box so I could check it.

We can now build an arm kernel (or at least the first steps).

I have pushed it out to kbuild-next.git.
And I will redo the patch series later so we do not bisect break arm etc.

	Sam

diff --git a/Makefile b/Makefile
index 2628295..4761b3b 100644
--- a/Makefile
+++ b/Makefile
@@ -328,7 +328,8 @@ AFLAGS_KERNEL	=
 # Use LINUXINCLUDE when you must reference the include/ directory.
 # Needed to be compatible with the O= option
 LINUXINCLUDE    := -Iinclude \
-                   $(if $(KBUILD_SRC),-Iinclude2 -I$(srctree)/include) \
+                   $(if $(KBUILD_SRC),                                 \
+                        -Iinclude2 -Iinclude3 -I$(srctree)/include)    \
                    -I$(srctree)/arch/$(hdr-arch)/include               \
                    -include include/linux/autoconf.h
 
@@ -913,6 +914,7 @@ PHONY += prepare archprepare prepare0 prepare1 prepare2 prepare3
 # and if so do:
 # 1) Check that make has not been executed in the kernel src $(srctree)
 # 2) Create the include2 directory, used for the second asm symlink
+# 3) Create the include3 directory, used for the third asm symlink
 prepare3: include/config/kernel.release
 ifneq ($(KBUILD_SRC),)
 	@echo '  Using $(srctree) as source for kernel'
@@ -925,6 +927,10 @@ ifneq ($(KBUILD_SRC),)
 	$(Q)if [ -e $(srctree)/include/asm-$(SRCARCH)/system.h ]; then  \
 	    ln -fsn $(srctree)/include/asm-$(SRCARCH) include2/asm;     \
 	    fi
+	$(Q)if [ ! -d include3 ]; then mkdir -p include3; fi;
+	$(Q)if [ -e $(srctree)/include/asm-$(SRCARCH)/system.h ]; then  \
+	    ln -fsn ../include/asm-$(SRCARCH) include3/asm;                \
+	    fi
 endif
 
 # prepare2 creates a makefile if using a separate output directory

  reply	other threads:[~2008-06-23 20:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23 16:22 linux-next build poblems Stephen Rothwell
2008-06-23 17:08 ` Sam Ravnborg
2008-06-23 23:29   ` Stephen Rothwell
2008-06-23 17:10 ` Russell King
2008-06-23 20:07   ` Sam Ravnborg
2008-06-23 20:21     ` Sam Ravnborg [this message]
2008-06-23 20:32       ` Russell King
2008-06-23 20:51         ` Sam Ravnborg
2008-06-23 21:01           ` Sam Ravnborg
2008-06-24 13:29       ` Stephen Rothwell

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=20080623202156.GA12027@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=hskinnemoen@atmel.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=sfr@canb.auug.org.au \
    /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.