linux-kernel - 3.8-rc[12] cpufreq build errors...

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

Message-ID: <50E83B2D.9000609@gmail.com>
Date:	Sat, 05 Jan 2013 09:39:41 -0500
From:	Woody Suwalski <terraluna977@...il.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
CC:	LKML <linux-kernel@...r.kernel.org>
Subject: 3.8-rc[12] cpufreq build errors...

Rafael, in 3.8 kernel part of the common logic has been moved to a 
separate cpufreq_governor.c file.
According to the Makefile, the cpufreq_governor.o is to be linked to 
other cpufreq  modules.

However I see that a separate malformed cpufreq_governor.ko is created, 
and then the real modules can not work without the common logic either.

The build config is a simple 32-bit config, on top of vanilla source.

I submit a verbose build log with "ls *.ko" and some "modinfo" outputs 
attached to the bottom.
Clearly the build subsystem is misinterpreting the build intentions.

Could you please check if you see the same issue in your builds?
I am using a 32-bit October-ish Debian Testing as a build machine (Eeepc 
netbook).

Thanks, Woody

View attachment "cpufreq.log" of type "text/x-log" (65329 bytes)

View attachment "config" of type "text/plain" (100926 bytes)