public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: Blaisorblade <blaisorblade@yahoo.it>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [BUG report] UML linux-2.6 latest BK doesn't compile
Date: Tue, 08 Feb 2005 13:29:09 -0500	[thread overview]
Message-ID: <200502081829.j18ITAs0003968@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Tue, 08 Feb 2005 10:09:55 GMT." <1107857395.15872.2.camel@imp.csi.cam.ac.uk>

aia21@cam.ac.uk said:
> arch/um/kernel/exec_kern.c:59: undefined reference to `__bb_init_func'

The __bb_init_func export is to allow modules to be built with a gcov-enabled
UML.  I get a bunch of undefines in the module links when I get rid of it.

This is probably being too intimate with libc, and yours probably doesn't have
__bb_init_func.

Try the patch below and see if it helps.  Modules won't work, but you should
get a working UML.

				Jeff
Index: 2.6.10/arch/um/kernel/Makefile
===================================================================
--- 2.6.10.orig/arch/um/kernel/Makefile	2005-02-07 12:45:56.000000000 -0500
+++ 2.6.10/arch/um/kernel/Makefile	2005-02-08 10:23:31.000000000 -0500
@@ -15,7 +15,6 @@
 
 obj-$(CONFIG_BLK_DEV_INITRD) += initrd.o
 obj-$(CONFIG_GPROF)	+= gprof_syms.o
-obj-$(CONFIG_GCOV)	+= gmon_syms.o
 obj-$(CONFIG_TTY_LOG)	+= tty_log.o
 obj-$(CONFIG_SYSCALL_DEBUG) += syscall_user.o
 
Index: 2.6.10/arch/um/kernel/gmon_syms.c
===================================================================
--- 2.6.10.orig/arch/um/kernel/gmon_syms.c	2004-12-24 16:35:39.000000000 -0500
+++ 2.6.10/arch/um/kernel/gmon_syms.c	2003-09-15 09:40:47.000000000 -0400
@@ -1,20 +0,0 @@
-/* 
- * Copyright (C) 2001, 2002 Jeff Dike (jdike@karaya.com)
- * Licensed under the GPL
- */
-
-#include "linux/module.h"
-
-extern void __bb_init_func(void *);
-EXPORT_SYMBOL(__bb_init_func);
-
-/*
- * Overrides for Emacs so that we follow Linus's tabbing style.
- * Emacs will notice this stuff at the end of the file and automatically
- * adjust the settings for this buffer only.  This must remain at the end
- * of the file.
- * ---------------------------------------------------------------------------
- * Local variables:
- * c-file-style: "linux"
- * End:
- */


  parent reply	other threads:[~2005-02-08 16:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-08 10:09 [BUG report] UML linux-2.6 latest BK doesn't compile Anton Altaparmakov
2005-02-08 10:22 ` Blaisorblade
2005-02-08 10:40   ` Anton Altaparmakov
2005-02-08 17:48     ` [uml-devel] " Blaisorblade
2005-02-08 22:21       ` Jeff Dike
2005-02-08 18:29 ` Jeff Dike [this message]
2005-02-08 17:37   ` Blaisorblade
2005-02-08 22:22     ` Jeff Dike
2005-02-14 11:35       ` Partial fix! - Was: " Anton Altaparmakov
2005-02-16 18:27         ` [uml-devel] " Blaisorblade
2005-03-05 19:45         ` Jeff Dike
2005-03-05 18:31           ` Adrian Bunk
2005-03-07 19:44           ` [uml-devel] " Blaisorblade
2005-03-08  0:10             ` Jeff Dike
2005-03-13 20:06               ` Blaisorblade
     [not found]                 ` <EBD0B8CF381E8B44BB99E8EA137E27C0021AD010@CPEXBE-EML06.kpnsp.local>
2006-09-09  9:31                   ` Blaisorblade
2006-09-11 15:27                     ` Jeff Dike

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=200502081829.j18ITAs0003968@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=aia21@cam.ac.uk \
    --cc=blaisorblade@yahoo.it \
    --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