linux-kernel - Re: linux-next: build failure after merge final merge

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]

Date:	Tue, 16 Feb 2010 10:41:55 -0700
From:	Bjorn Helgaas <bjorn.helgaas@...com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Jesse Barnes <jbarnes@...tuousgeek.org>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	David Miller <davem@...emloft.net>
Subject: Re: linux-next: build failure after merge final merge

On Tuesday 16 February 2010 10:03:29 am Bjorn Helgaas wrote:
> On Tuesday 16 February 2010 12:36:50 am Stephen Rothwell wrote:
> > After merging, today's linux-next build (sparc64 defconfig) failed like
> > this:
> > 
> > arch/sparc/kernel/pci.c: In function 'pci_cfg_fake_ranges':
> > arch/sparc/kernel/pci.c:404: error: 'struct pci_bus' has no member named 'resource'
> 
> Huh.  I built sparc64 defconfig (and alpha, arm, i686, ia64, mips,
> powerpc, sh, and sparc) in Jesse's linux-next branch, but obviously
> that's not doing the right thing for some reason.

BTW, do you have cross-compilers for all those targets?  It'd be great
if they were all available somewhere.  My set is incomplete and getting
old.

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