linux-kernel - Re: compile error in current 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]

Date:	Fri, 25 Jan 2008 14:17:31 -0800
From:	Greg KH <gregkh@...e.de>
To:	Jeremy Fitzhardinge <jeremy@...p.org>,
	Randy Dunlap <rdunlap@...otime.net>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: compile error in current git

On Fri, Jan 25, 2008 at 12:36:55PM -0800, Jeremy Fitzhardinge wrote:
> When compiling current git with CONFIG_BLOCK disabled, I'm seeing this 
> compile error:
>
>  CC      drivers/base/core.o
> /home/jeremy/hg/xen/paravirt/linux/drivers/base/core.c: In function 
> ???device_add_class_symlinks???:
> /home/jeremy/hg/xen/paravirt/linux/drivers/base/core.c:655: error: 
> ???part_type??? undeclared (first use in this function)
> /home/jeremy/hg/xen/paravirt/linux/drivers/base/core.c:655: error: (Each 
> undeclared identifier is reported only once
> /home/jeremy/hg/xen/paravirt/linux/drivers/base/core.c:655: error: for each 
> function it appears in.)
> /home/jeremy/hg/xen/paravirt/linux/drivers/base/core.c: In function 
> ???device_remove_class_symlinks???:
> /home/jeremy/hg/xen/paravirt/linux/drivers/base/core.c:728: error: 
> ???part_type??? undeclared (first use in this function)
> make[4]: *** [drivers/base/core.o] Error 1

Hm, I thought we fixed the CONFIG_BLOCK disabled issues with Randy's
older patch.  Randy, wasn't this already addressed somehow?

Jeremy, do you have a .config I can use to try to duplicate and fix
this?

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/