linux-kernel - Re: Kbuild changes since 2.6.21??

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]

Message-ID: <20080528184220.GA6055@uranus.ravnborg.org>
Date:	Wed, 28 May 2008 20:42:20 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Doug Reiland <dreiland@...il.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Kbuild changes since 2.6.21??

On Wed, May 28, 2008 at 02:27:47PM -0400, Doug Reiland wrote:
> By bad, drivers/power/Makefile is ok.
> I thought I reproduced the issue there.
> 
> On Wed, May 28, 2008 at 12:23 PM, Doug Reiland <dreiland@...il.com> wrote:
> > There are some makefiles that look at CONFIG_XXXX variables to make
> > decisions. For example, drivers/power/Makefile has the following
> > lines:
> >
> > ifeq ($(CONFIG_SYSFS),y)
> > power_supply-objs += power_supply_sysfs.o
> > endif
> >
> >
> > If I run make clean or make mrproper, it doesn't see CONFIG_SYSFS set
> > anymore so it doesn't cleanup power_supply_sysfs.o.
> >
> > This is for 2.6.25, but I think this use to work for 2.6.21. I am
> > using drivers/power/Makefile as an example, but I am seeing the same
> > thing for my driver's Makefile.

We use find to delete all .o files. So the content of your Kbuild file
should not matter here.
Can you describe the setup where you see the issue?

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