From: Morten Helgesen <morten.helgesen@nextframe.net>
To: Seiichi Nakashima <nakasima@kumin.ne.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux-2.5.11 compile error ( without framebuffer )
Date: Mon, 29 Apr 2002 13:56:21 +0200 [thread overview]
Message-ID: <20020429135621.B118@sexything> (raw)
In-Reply-To: <200204291142.AA00055@prism.kumin.ne.jp>
Hi, Seiichi
On Mon, Apr 29, 2002 at 08:42:46PM +0900, Seiichi Nakashima wrote:
> Hi.
>
> I compile linux-2.5.11 ( gcc-2.95.3 ), but compile error occured at framebuffer.
> Then I recompile linux-2.5.11 without framebuffer, but compile error again.
>
>
> ide.c: In function `reset_pollfunc':
> ide.c:603: warning: assignment discards qualifiers from pointer target type
> eepro100.c:2252: warning: `eepro100_remove_one' defined but not used
just warnings ...
> bluesmoke.c: In function `intel_thermal_interrupt':
> bluesmoke.c:36: warning: implicit declaration of function `ack_APIC_irq'
> bluesmoke.c: In function `intel_init_thermal':
> bluesmoke.c:92: warning: implicit declaration of function `apic_read'
> bluesmoke.c:104: warning: implicit declaration of function `apic_write_around'
> arch/i386/kernel/kernel.o: In function `intel_thermal_interrupt':
> arch/i386/kernel/kernel.o(.text+0x7221): undefined reference to `ack_APIC_irq'
> arch/i386/kernel/kernel.o: In function `intel_init_thermal':
> arch/i386/kernel/kernel.o(.text.init+0x2ad2): undefined reference to `apic_read'
> arch/i386/kernel/kernel.o(.text.init+0x2b12): undefined reference to `apic_write_around'
> arch/i386/kernel/kernel.o(.text.init+0x2b31): undefined reference to `apic_read'
> arch/i386/kernel/kernel.o(.text.init+0x2b41): undefined reference to `apic_write_around'
> make: *** [vmlinux] Error 1
well, the P4/Xeon Thermal stuff depends on APIC support ... bluesmoke.c uses
ack_APIC_irq() and friends.
>
> --------------------------------
> Seiichi Nakashima
> Email nakasima@kumin.ne.jp
> --------------------------------
> -
> 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/
== Morten
--
"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-04-29 11:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-29 11:42 linux-2.5.11 compile error ( without framebuffer ) Seiichi Nakashima
2002-04-29 11:56 ` Morten Helgesen [this message]
2002-04-29 21:21 ` Seiichi Nakashima
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=20020429135621.B118@sexything \
--to=morten.helgesen@nextframe.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nakasima@kumin.ne.jp \
/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