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: <adad5017zpt.fsf@cisco.com>
Date:	Tue, 12 Jun 2007 12:13:50 -0700
From:	Roland Dreier <rdreier@...co.com>
To:	linux-kernel@...r.kernel.org,
	"Natalie.Protasevich@...sys.com" <Natalie.Protasevich@...sys.com>,
	Vivek Goyal <vgoyal@...ibm.com>
Cc:	akpm@...ux-foundation.org
Subject: CONFIG_X86_ES7000=y, CONFIG_X86_GENERICARCH=n, CONFIG_ACPI=y build broken

(sending to Vivek since he seems to be one of the last people to touch
this code)

For some strange reason I found myself compiling a kernel with
CONFIG_X86_ES7000 and CONFIG_ACPI set and CONFIG_X86_GENERICARCH not
set.  It died with

    arch/i386/kernel/built-in.o: In function `acpi_parse_madt':
    boot.c:(.init.text+0x68b7): undefined reference to `acpi_madt_oem_check'
    arch/i386/kernel/built-in.o: In function `get_smp_config':
    (.init.text+0x9f98): undefined reference to `mps_oem_check'
    arch/i386/kernel/built-in.o: In function `connect_bsp_APIC':
    (.init.text+0xa340): undefined reference to `enable_apic_mode'
    arch/i386/kernel/built-in.o: In function `connect_bsp_APIC':
    (.init.text+0xa370): undefined reference to `enable_apic_mode'

this seems to be because eg acpi_madt_oem_check() and mps_oem_check()
are defined in arch/i386/mach-generic/es7000.c, but arch/i386/Makefile
only goes into mach-generic if CONFIG_X86_GENERICARCH is set.
I didn't track down why enable_apic_mode is broken yet.

No patch because I don't understand how this subarch stuff is supposed
to build :(

 - R.
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ