From: Allan Duncan <allan.d@bigpond.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux v2.5.47
Date: Mon, 11 Nov 2002 23:06:10 +1100 [thread overview]
Message-ID: <3DCF9D32.8070006@bigpond.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0211101944030.17742-100000@penguin.transmeta.com>
Two failures to build a kernel for me - 1 new, one old:
New - undefined refs if CONFIG_CRYPTO is not set.
Old - undefined refs if aout is a module - use a patch from 2.5.46
(ignore the dates, I just hacked the previous one for an offset of 495):
--- a/kernel/ksyms.c Tue Nov 5 16:33:06 2002
+++ b/kernel/ksyms.c Tue Nov 5 16:36:40 2002
@@ -53,6 +53,7 @@
#include <linux/percpu.h>
#include <linux/smp_lock.h>
#include <linux/dnotify.h>
+#include <linux/ptrace.h>
#include <asm/checksum.h>
#if defined(CONFIG_PROC_FS)
@@ -492,6 +495,7 @@
#if !defined(__ia64__)
EXPORT_SYMBOL(loops_per_jiffy);
#endif
+EXPORT_SYMBOL(ptrace_notify);
/* misc */
next prev parent reply other threads:[~2002-11-11 11:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 3:46 Linux v2.5.47 Linus Torvalds
2002-11-11 8:10 ` Adrian Bunk
2002-11-11 12:06 ` Allan Duncan [this message]
2002-11-11 14:14 ` Linux v2.5.47 (CONFIG_CRYPTO) James Morris
2002-11-11 23:32 ` Linux v2.5.47 Adrian Bunk
2002-11-13 0:22 ` Christoph Hellwig
2002-11-13 1:03 ` Alan Cox
2002-11-13 0:43 ` Christoph Hellwig
2002-11-13 12:03 ` Michael Still
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=3DCF9D32.8070006@bigpond.com \
--to=allan.d@bigpond.com \
--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