lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <4E4B0D28.7010905@linux.intel.com>
Date:	Tue, 16 Aug 2011 17:36:56 -0700
From:	Darren Hart <dvhart@...ux.intel.com>
To:	"lkml, " <linux-kernel@...r.kernel.org>
CC:	Paul Mackerras <paulus@...ba.org>, Gary Thomas <gary@...assoc.com>,
	"Woodhouse, David" <david.woodhouse@...el.com>
Subject: can't build modules after clean for powerpc

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ