mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Sachin Kamat <sachin.kamat@samsung.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: Build error - vmlinux.lds [Re: linux-next: Tree for Jun 18]
Date: Wed, 18 Jun 2014 13:20:21 +0100	[thread overview]
Message-ID: <20140618122020.GB32514@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAK5sBcEg1XYQmzshxdLDHFCYFiawV0d8rt7aeAkPoiPhNMX1CQ@mail.gmail.com>

On Wed, Jun 18, 2014 at 05:38:14PM +0530, Sachin Kamat wrote:
> On Wed, Jun 18, 2014 at 5:26 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > On Wed, Jun 18, 2014 at 04:50:43PM +0530, Sachin Kamat wrote:
> >> Hi,
> >>
> >> I observe the following build error while building uImage for ARM.
> >>
> >>   Kernel: arch/arm/boot/Image is ready
> >> make[2]: *** No rule to make target
> >> `arch/arm/boot/compressed/vmlinux.lds', needed by
> >> `arch/arm/boot/compressed/vmlinux'.  Stop.
> >> make[1]: *** [arch/arm/boot/compressed/vmlinux] Error 2
> >> make: *** [uImage] Error 2
> >
> > Works fine here against an empty object tree:
> >
> > http://www.arm.linux.org.uk/developer/build/file.php?lid=9591
> >
> > Are you building into an already-built object tree or rebuilding an
> > already built tree?
> 
> I did a clean build after updating the tree to next-20140618.
> git status show me the following after doing make clean
> 
> # On branch master
> # Changes not staged for commit:
> #   (use "git add/rm <file>..." to update what will be committed)
> #   (use "git checkout -- <file>..." to discard changes in working directory)
> #
> #    deleted:    arch/arm/boot/compressed/vmlinux.lds.S
> 
> 
> My tip of kernel points to commit 4ca1fbc122fcb ("Add linux-next specific
> files for 20140618")
> 
> >
> > This is likely caused by make getting confused over the dependencies.
> > I suggest making clean to recover from this error.
> 
> I get this error when I do a clean build too.

Hmm.  Please try removing vmlinux.lds.S from extra-y in
arch/arm/boot/compressed/Makefile and restoring the deleted file.

-- 
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.

  reply	other threads:[~2014-06-18 12:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-18 11:20 Sachin Kamat
2014-06-18 11:56 ` Russell King - ARM Linux
2014-06-18 12:08   ` Sachin Kamat
2014-06-18 12:20     ` Russell King - ARM Linux [this message]
2014-06-19  3:40       ` Sachin Kamat

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=20140618122020.GB32514@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sachin.kamat@samsung.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®