From: Nathan <wfilardo@fuse.net>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.5-dj2 compile failures
Date: Tue, 26 Feb 2002 22:57:36 -0500 [thread overview]
Message-ID: <3C7C5930.6010703@fuse.net> (raw)
In-Reply-To: <3C7C4BBF.2020505@fuse.net>
This *might * just be a FAQ, but I think it's actually a
Makefile bug (it's happened twice, each time after a make mrproper).
$ strings vmlinux | grep __ver
__verify_write_Rsmp_203afbeb
vmalloc_to_page_R__ver_vmalloc_to_page
idle_cpu_R__ver_idle_cpu
set_cpus_allowed_R__ver_set_cpus_allowed
The first is not a problem, but the rest are. Grepping
include/linux/modules/* gave no matches:
$ find include/linux/modules/* | xargs grep -e idle_cpu
$ find include/linux/modules/* | xargs grep -e set_cpu
$ find include/linux/modules/* | xargs grep -e vmalloc_to_page
Config (I think this is all that matters... if something else is needed,
lemme know.):
CONFIG_X86=y
CONFIG_ISA=y
# CONFIG_SBUS is not set
CONFIG_UID16=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
#
# General setup
#
CONFIG_NET=y
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y
#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
CONFIG_MPENTIUMIII=y
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MELAN is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_X86_TSC=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_PGE=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
CONFIG_MICROCODE=m
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM4G_HIGHPTE is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_HIGHMEM64G_HIGHPTE is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
CONFIG_SMP=y
CONFIG_PREEMPT=y
# CONFIG_MULTIQUAD is not set
CONFIG_HAVE_DEC_LOCK=y
next prev parent reply other threads:[~2002-02-27 3:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 3:00 2.5.5-dj2 compile failures Nathan
2002-02-27 3:57 ` Nathan [this message]
2002-02-27 4:06 ` Greg KH
2002-02-27 12:24 ` Helge Hafting
2002-02-27 14:01 ` Zwane Mwaikambo
2002-02-27 14:17 ` Roberto Nibali
2002-02-27 14:16 ` Zwane Mwaikambo
2002-02-27 14:45 ` Martin Dalecki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C7C5930.6010703@fuse.net \
--to=wfilardo@fuse.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.