linux-kernel - Re: [build bug] drivers/ssb build failure, latest -git

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

Message-ID: <20071015173840.GA26109@elte.hu>
Date:	Mon, 15 Oct 2007 19:38:40 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Michael Buesch <mb@...sch.de>
Cc:	Al Viro <viro@....linux.org.uk>, gregkh@...e.de,
	David Brownell <dbrownell@...rs.sourceforge.net>,
	"John W. Linville" <linville@...driver.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [build bug] drivers/ssb build failure, latest -git


* Ingo Molnar <mingo@...e.hu> wrote:

> > > there's a new build failure with latest -git:
> > > 
> > >  drivers/built-in.o: In function `ssb_ohci_probe':
> > >  ohci-hcd.c:(.text+0xbff39): undefined reference to `ssb_device_enable'
> > >  ohci-hcd.c:(.text+0xbff6f): undefined reference to `ssb_admatch_base'
> > >  ohci-hcd.c:(.text+0xbff8b): undefined reference to `ssb_admatch_size'
> > >  ohci-hcd.c:(.text+0xbffe5): undefined reference to `ssb_device_disable'
> > >  [...]
> > > 
> > > config attached.

> > I'm not sure why this happens. SSB is Y and ohci-hcd is also Y. So 
> > why doesn't it find the syms?
> 
> hm, it builds fine now. Weird - i'll double-check i got the right 
> config.

find attached another config that reproduces the build failure above.

i think the reason is this:

CONFIG_SSB=m
CONFIG_USB_OHCI_HCD=y
CONFIG_USB_OHCI_HCD_SSB=y

	Ingo
-
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/