linux-kernel - Re: The longest build error ever, ever, ever seen :) (Re:linux-next: Tree for November 26)

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-prev] [day] [month] [year] [list]

Date:	Wed, 1 Dec 2010 11:29:38 -0800
From:	Greg KH <gregkh@...e.de>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	Milton Miller <miltonm@....com>, linux-next@...r.kernel.org,
	Zimny Lech <napohybelskurwysynom2010@...il.com>,
	Valdis Kletnieks <Valdis.Kletnieks@...edu>,
	linux-kernel@...r.kernel.org
Subject: Re: The longest build error ever, ever, ever seen :)
 (Re:linux-next: Tree for November 26)

On Wed, Dec 01, 2010 at 10:30:35AM -0800, Randy Dunlap wrote:
> On Sun, 28 Nov 2010 00:55:14 -0600 Milton Miller wrote:
> 
> [also adding linux-next back to cc: list]
> 
> 
> > On Sat Nov 27 2010 around 13:13:03 EST, Valdis Kletnieks wrote:
> > > On Sat, 27 Nov 2010 08:45:55 PST, Greg KH said:
> > > > On Sat, Nov 27, 2010 at 09:56:45AM +0100, Zimny Lech wrote:
> > > > > Ave!
> > > > >
> > > > > 2010/11/26 Stephen Rothwell <sfr@...xxxxxxxxxxxxx>:
> > > > > > Hi all,
> > > > > >
> > > > >
> > > > > OMG, LOL, this one is awesome :) The longest build error ever, ever,
> > > > > ever seen! Fscking awesome, someone gets Guiness World Record :)
> > > > >
> > > > > LD drivers/staging/built-in.o
> > > > > drivers/staging/rtl8192e/built-in.o: In function `rtl8192_setBBreg':
> > > > > (.text+0xae00): multiple definition of `rtl8192_setBBreg'
> > > > > drivers/staging/rtl8192u/built-in.o:(.text+0xa1a0): first defined here
> > > >
> > > > You built both of these drivers into the kernel, which causes the
> > > > problem. Try building them as modules, or just one as a module, and
> > > > that will solve the problem.
> > > 
> > > We probably should create some Kconfig magic to prevent this situation?
> > > 
> > > depends (othermodule != 'y') || (myself != 'y')
> > > 
> > > or am I on the wrong track here?
> > > 
> > 
> > A simple
> > 
> > depends on !OTHERMODULE
> > 
> > allows either to be built-in or both to be modular.
> > 
> > It also documents what conflicts.
> > 
> > (see Menu dependencies in Documentation/kbuild/kconfig-language.txt)
> 
> When added for 2 drivers that should not both be built-in, that
> causes this error message:
> 
> drivers/staging/rtl8192u/Kconfig:1:error: recursive dependency detected!
> drivers/staging/rtl8192u/Kconfig:1:     symbol RTL8192U depends on RTL8192E
> drivers/staging/rtl8192e/Kconfig:1:     symbol RTL8192E depends on RTL8192U
> 
> but yes, only one driver is then built-in.

Just make both drivers only able to be built as a module, which will
make everything work properly and all will be happy :)

thanks,

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/