From: Christian Kujau <evil@g-house.de>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.71 compile error on alpha
Date: Tue, 17 Jun 2003 20:05:18 +0200 [thread overview]
Message-ID: <3EEF585E.9030404@g-house.de> (raw)
In-Reply-To: <wrpr85te3fa.fsf@hina.wild-wind.fr.eu.org>
Marc Zyngier schrieb:
> Please try this patch :
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=105540998415031&w=2
>
ok, that did it, but then another error showed up:
[...]
AS arch/alpha/lib/stxcpy.o
AS arch/alpha/lib/stxncpy.o
CC arch/alpha/lib/udelay.o
AR arch/alpha/lib/lib.a
CPP arch/alpha/vmlinux.lds.s
GEN .version
CHK include/linux/compile.h
UPD include/linux/compile.h
CC init/version.o
LD init/built-in.o
LD vmlinux
net/built-in.o(.init.text+0x484): In function `flow_cache_init':
: undefined reference to `register_cpu_notifier'
net/built-in.o(.init.text+0x488): In function `flow_cache_init':
: undefined reference to `register_cpu_notifier'
make: *** [vmlinux] Error 1
lila:/usr/src/linux-2.5#
oh, just before vmlinux was made! before & after applying the patch i
did "make clean" (do i have to make clean "before" applying patches
anyway? after applying patches and before making targets, yes.)
oh, and this alpha is named "Avanti" but a kernel compile needs 80mins
or so :-)
Thank you,
Christian.
next prev parent reply other threads:[~2003-06-17 17:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 22:52 2.5.71 compile error on alpha Christian Kujau
2003-06-16 23:00 ` Måns Rullgård
2003-06-17 12:16 ` Ivan Kokshaysky
2003-06-17 18:33 ` Christian Kujau
[not found] ` <wrpr85te3fa.fsf@hina.wild-wind.fr.eu.org>
2003-06-17 18:05 ` Christian Kujau [this message]
2003-06-17 18:26 ` Måns Rullgård
2003-06-17 20:22 ` Jan-Benedict Glaw
2003-06-17 20:33 ` Christian Kujau
2003-06-17 21:20 ` Måns Rullgård
2003-06-17 22:27 ` Christian Kujau
2003-06-18 19:36 ` Geert Uytterhoeven
2003-06-17 21:00 ` Christian Kujau
2003-06-17 21:00 ` Christian Kujau
2003-06-17 21:23 ` Måns Rullgård
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=3EEF585E.9030404@g-house.de \
--to=evil@g-house.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 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.