public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: "lkml, " <linux-kernel@vger.kernel.org>
Cc: Paul Mackerras <paulus@samba.org>,
	Gary Thomas <gary@mlbassoc.com>,
	"Woodhouse, David" <david.woodhouse@intel.com>
Subject: can't build modules after clean for powerpc
Date: Tue, 16 Aug 2011 17:36:56 -0700	[thread overview]
Message-ID: <4E4B0D28.7010905@linux.intel.com> (raw)

According to the Makefile comments and
Documentation/kconfig/makefile.txt, make clean should leave enough
intact to build modules with:

###
# Cleaning is done on three levels.
# make clean     Delete most generated files
#                Leave enough to build external modules

The following line in the arch/powerpc/Makefile prevents that from working:

KBUILD_LDFLAGS_MODULE += arch/powerpc/lib/crtsavres.o

External module compilation fails to link as it can't find
arch/powerpc/lib/crtsavres.o.

It appears from the make logs that crtsavres.o is linked in to
built-in.o, and thus vmlinux. If that is the case, it doesn't seem like
crtsavres.o should need to be singled out. What am I missing here?

If I comment it out:

#KBUILD_LDFLAGS_MODULE += arch/powerpc/lib/crtsavres.o

my example module builds successfully.

If it is necessary, then we need a means to instruct the top level
makefile to not delete it during "clean". Is there such a directive?

KBUILD_CLEAN_EXCLUDE_MODULES or something?

Thanks,

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel

             reply	other threads:[~2011-08-17  0:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-17  0:36 Darren Hart [this message]
2011-08-17  7:49 ` can't build modules after clean for powerpc Sam Ravnborg
2011-08-17 19:02   ` Darren Hart

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=4E4B0D28.7010905@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=david.woodhouse@intel.com \
    --cc=gary@mlbassoc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.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