linux-kernel - Re: [BUILD-FAILURE] next-20090114

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 14 Jan 2009 10:50:29 -0800
From:	Greg KH <gregkh@...e.de>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [BUILD-FAILURE] next-20090114 - drivers/staging/meilhaus

On Wed, Jan 14, 2009 at 10:11:58AM -0800, Randy Dunlap wrote:
> Greg KH wrote:
> > On Wed, Jan 14, 2009 at 11:30:24PM +0530, Kamalesh Babulal wrote:
> >> Hi Stephen,
> >>
> >> 	next-20090114 randconfig build on x86_64 machine fails,
> >>
> >>   LD      drivers/staging/meilhaus/built-in.o
> >> drivers/staging/meilhaus/me1600.o: In function `cleanup_module':
> >> (.exit.text+0x0): multiple definition of `cleanup_module'
> >> drivers/staging/meilhaus/memain.o:memain.c:(.exit.text+0x0): first defined here
> > 
> > Yeah, a lot of these staging drivers can't handle being built into the
> > kernel.
> > 
> > At first glance, I don't see a way to prevent this, is there some
> > Kconfig option I can use to say, "this can only be a module or disabled,
> > not build statically"?
> 
> 	depends on m

Doh, it's even documented!

Thanks, I'll go fix that all up.

greg k-h
--
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/