From: Rolf Eike Beer <eike@euklid.math.uni-mannheim.de>
To: linux-kernel@vger.kernel.org
Subject: 2.4.11-pre6: redefined & Unresolved symbols
Date: Tue, 09 Oct 2001 13:55:32 +0200 [thread overview]
Message-ID: <1167435.cZxFsPTIob@newssend.sf-tec.de> (raw)
This is printed at least 50 times during make bzImage and make modules:
In file included from
/usr/src/linux-2.4.11-pre6/drivers/acpi/include/platform/aclinux.h:56,
from
/usr/src/linux-2.4.11-pre6/drivers/acpi/include/platform/acenv.h:109,
from
/usr/src/linux-2.4.11-pre6/drivers/acpi/include/acpi.h:35,
from sm_osl.c:39:
/usr/src/linux-2.4.11-pre6/drivers/acpi/include/platform/acgcc.h:104:
warning: `wbinvd' redefined
/usr/src/linux-2.4.11-pre6/include/asm/system.h:128: warning: this is
the location of the previous definition
And this is of course from make modules
depmod: *** Unresolved symbols in
/lib/modules/2.4.11-pre6/kernel/drivers/acpi/ospm/busmgr/ospm_busmgr.o
depmod: acpi_ut_debug_print_raw
depmod: acpi_ut_debug_print
depmod: acpi_ut_status_exit
depmod: acpi_ut_exit
depmod: acpi_ut_trace
depmod: *** Unresolved symbols in
/lib/modules/2.4.11-pre6/kernel/drivers/acpi/ospm/button/ospm_button.o
depmod: acpi_ut_debug_print_raw
depmod: acpi_ut_debug_print
depmod: acpi_ut_status_exit
depmod: acpi_ut_trace
depmod: *** Unresolved symbols in
/lib/modules/2.4.11-pre6/kernel/drivers/acpi/ospm/processor/ospm_processor.o
depmod: acpi_ut_debug_print_raw
depmod: acpi_ut_debug_print
depmod: acpi_ut_status_exit
depmod: acpi_ut_trace
depmod: *** Unresolved symbols in
/lib/modules/2.4.11-pre6/kernel/drivers/acpi/ospm/system/ospm_system.o
depmod: acpi_ut_debug_print_raw
depmod: acpi_ut_debug_print
depmod: acpi_ut_status_exit
depmod: acpi_ut_trace
It's a 2.4.11-pre6 without any modifications.
Eike Beer
reply other threads:[~2001-10-09 11:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1167435.cZxFsPTIob@newssend.sf-tec.de \
--to=eike@euklid.math.uni-mannheim.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox