From: Morten Helgesen <morten.helgesen@nextframe.net>
To: "Hanno Böck" <hanno@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.22 compile problems
Date: Mon, 17 Jun 2002 13:11:23 +0200 [thread overview]
Message-ID: <20020617131123.A129@sexything> (raw)
In-Reply-To: <20020617125905.5511b12c.hanno@gmx.de>
enable APIC support ... the intel thermal stuff depends on it.
On Mon, Jun 17, 2002 at 12:59:05PM +0200, Hanno B?ck wrote:
> I tried to compile 2.5.22 and got the following errors:
>
> ld -m elf_i386 -r -o init.o main.o version.o do_mounts.o
> make[1]: Verlassen des Verzeichnisses Verzeichnis »/usr/src/linux-2.5.22/init«
> ld -m elf_i386 -T /usr/src/linux-2.5.22/arch/i386/vmlinux.lds -e stext arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/init.o --start-group arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o /usr/src/linux-2.5.22/arch/i386/lib/lib.a lib/lib.a /usr/src/linux-2.5.22/arch/i386/lib/lib.a drivers/built-in.o sound/sound.o arch/i386/pci/pci.o net/network.o --end-group -o vmlinux
> arch/i386/kernel/kernel.o: In function `intel_thermal_interrupt':
> arch/i386/kernel/kernel.o(.text+0x7821): undefined reference to `ack_APIC_irq'
> arch/i386/kernel/kernel.o: In function `intel_init_thermal':
> arch/i386/kernel/kernel.o(.text.init+0x1450): undefined reference to `apic_read'
> arch/i386/kernel/kernel.o(.text.init+0x149b): undefined reference to `apic_write_around'
> arch/i386/kernel/kernel.o(.text.init+0x14cd): undefined reference to `apic_read'
> arch/i386/kernel/kernel.o(.text.init+0x14e0): undefined reference to `apic_write_around'
> make: *** [vmlinux] Fehler 1
>
>
>
> I have tried kernels 2.5.18, 2.5.20, 2.5.21 and 2.5.22 and I always had compile problems. Can't someone test the kernel-source with all options activated before it is released?
> I think it doesn't matter if this happens sometimes in the 2.5-series, but it should not become usual.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
"Livet er ikke for nybegynnere" - sitat fra en klok person.
mvh
Morten Helgesen
UNIX System Administrator & C Developer
Nextframe AS
admin@nextframe.net / 93445641
http://www.nextframe.net
next prev parent reply other threads:[~2002-06-17 11:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-17 10:59 2.5.22 compile problems Hanno Böck
2002-06-17 10:50 ` Zwane Mwaikambo
2002-06-17 11:11 ` Morten Helgesen [this message]
2002-06-17 11:55 ` [PATCH][2.5] Make SMP/APIC config option earlier Zwane Mwaikambo
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=20020617131123.A129@sexything \
--to=morten.helgesen@nextframe.net \
--cc=hanno@gmx.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