public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Jeff Dike <jdike@addtoit.com>
Cc: Blaisorblade <blaisorblade@yahoo.it>,
	lkml <linux-kernel@vger.kernel.org>,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Partial fix! - Was: Re: [BUG report] UML linux-2.6 latest BK doesn't compile
Date: Mon, 14 Feb 2005 11:35:03 +0000	[thread overview]
Message-ID: <1108380903.22656.9.camel@imp.csi.cam.ac.uk> (raw)
In-Reply-To: <200502082223.j18MMxs0013724@ccure.user-mode-linux.org>

On Tue, 2005-02-08 at 17:22 -0500, Jeff Dike wrote:
> blaisorblade@yahoo.it said:
> > Why not simply disable CONFIG_GCOV for him, in this case? 
> 
> Anton presumably turned on CONFIG_GCOV because he wanted to do some profiling...

Yes.  I finally found a way to get it to compile.  Compiling without TT
mode and WITHOUT static build it still fails with the same problem
(__bb_init_func problem I already reported).  But compiling without TT
but WITH static build the __bb_init_func problem goes away but instead I
get a __gcov_init missing symbol in my modules.

Note I have gcc-3.3.4-11 (SuSE 9.2) and it defines __gcov_init.  So I
added this as an export symbol and lo and behold the kernel and modules
compiled and I am now up an running with UML and NTFS as a module.  (-:

Here is the patch that I used to fix this:

--- ntfs-2.6-devel/arch/um/kernel/gmon_syms.c.old	2005-02-14 11:27:04.789474410 +0000
+++ ntfs-2.6-devel/arch/um/kernel/gmon_syms.c	2005-02-14 11:26:49.191117739 +0000
@@ -8,6 +8,9 @@
 extern void __bb_init_func(void *);
 EXPORT_SYMBOL(__bb_init_func);
 
+extern void __gcov_init(void *);
+EXPORT_SYMBOL(__gcov_init);
+
 /*
  * Overrides for Emacs so that we follow Linus's tabbing style.
  * Emacs will notice this stuff at the end of the file and automatically

Best regards,

        Anton
-- 
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/



  reply	other threads:[~2005-02-14 11:36 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
2005-02-08 17:37   ` Blaisorblade
2005-02-08 22:22     ` Jeff Dike
2005-02-14 11:35       ` Anton Altaparmakov [this message]
2005-02-16 18:27         ` [uml-devel] Partial fix! - Was: " 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=1108380903.22656.9.camel@imp.csi.cam.ac.uk \
    --to=aia21@cam.ac.uk \
    --cc=blaisorblade@yahoo.it \
    --cc=jdike@addtoit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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