linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: Anton Altaparmakov <aia21@cam.ac.uk>, Jeff Dike <jdike@addtoit.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: [BUG report] UML linux-2.6 latest BK doesn't compile
Date: Tue, 8 Feb 2005 18:37:22 +0100	[thread overview]
Message-ID: <200502081837.22519.blaisorblade@yahoo.it> (raw)
In-Reply-To: <200502081829.j18ITAs0003968@ccure.user-mode-linux.org>

On Tuesday 08 February 2005 19:29, Jeff Dike wrote:
> 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.

Why not simply disable CONFIG_GCOV for him, in this case?

Sorry for my previous answer, I was misleaded by the error message (which 
*does not* make sense). And it's the first time anybody sees a such error 
message, in my experience, so please post more details about your glibc (and 
whether gcov is installed).
-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  parent reply	other threads:[~2005-02-08 17:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1107857395.15872.2.camel@imp.csi.cam.ac.uk>
2005-02-08 10:22 ` [uml-devel] Re: [BUG report] UML linux-2.6 latest BK doesn't compile Blaisorblade
2005-02-08 10:40   ` Anton Altaparmakov
2005-02-08 17:48     ` Blaisorblade
2005-02-08 22:21       ` Jeff Dike
     [not found] ` <200502081829.j18ITAs0003968@ccure.user-mode-linux.org>
2005-02-08 17:37   ` Blaisorblade [this message]
2005-02-08 22:22     ` Jeff Dike
2005-02-14 11:35       ` [uml-devel] Partial fix! - Was: " Anton Altaparmakov
2005-02-16 18:27         ` Blaisorblade
2005-03-05 19:45         ` [uml-devel] " Jeff Dike
2005-03-05 18:31           ` Adrian Bunk
2005-03-07 19:44           ` Blaisorblade
2005-03-08  0:10             ` Jeff Dike
2005-03-13 20:06               ` Blaisorblade
2006-09-08 22:25                 ` [uml-devel] " i.r.wezeman
2006-09-09  9:31                   ` Blaisorblade
     [not found]                     ` <EBD0B8CF381E8B44BB99E8EA137E27C0021AD015@CPEXBE-EML06.kpnsp.local>
2006-09-09 15:30                       ` Blaisorblade
2006-09-11 15:27                     ` Jeff Dike
2006-09-17 18:04                       ` Blaisorblade

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=200502081837.22519.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=aia21@cam.ac.uk \
    --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