mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: Jeff Dike <jdike@addtoit.com>,
	lkml <linux-kernel@vger.kernel.org>,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [BUG report] UML linux-2.6 latest BK doesn't compile
Date: Tue, 08 Feb 2005 10:40:54 +0000	[thread overview]
Message-ID: <1107859254.582.4.camel@imp.csi.cam.ac.uk> (raw)
In-Reply-To: <200502081122.22613.blaisorblade@yahoo.it>

On Tue, 2005-02-08 at 11:22 +0100, Blaisorblade wrote:
> On Tuesday 08 February 2005 11:09, Anton Altaparmakov wrote:
> > Hi,
> >
> > With the current linux-2.6 BK tree I get this when trying to compile
> > UML:
> >
> >   CC      init/version.o
> >   LD      init/built-in.o
> >   LD      .tmp_vmlinux1
> > arch/um/kernel/built-in.o(__ksymtab+0x2b0): In function `um_execve':
> > arch/um/kernel/exec_kern.c:59: undefined reference to `__bb_init_func'
> > collect2: ld returned 1 exit status
> >   KSYM    .tmp_kallsyms1.S
> > nm: '.tmp_vmlinux1': No such file
> > /bin/bash: line 1: 26161 Exit 1                  nm -n .tmp_vmlinux1
> >      26162 Segmentation fault      | scripts/kallsyms >.tmp_kallsyms1.S
> > make: *** [.tmp_kallsyms1.S] Error 139
> >
> > This is with SKAS mode enabled and TT disabled.  My .config is attached.
> 
> Hmm - I do not understand at all where `__bb_init_func' comes from (not from 
> UML by sure, only from kernel headers possibly). And from preprocessing the 
> source (of the -bk4 snapshot), nothing similar comes out.

It is from UML.  'bk -r grep __bb_init_func' gives:

arch/um/kernel/gmon_syms.c      1.1     extern void __bb_init_func(void
*);
arch/um/kernel/gmon_syms.c      1.1     EXPORT_SYMBOL(__bb_init_func);

The kernel compiles fine with the same .config but TT mode also enabled.

So I suspect that in the non-TT case the gmon_syms binary doesn't get
linked into the kernel so the symbol is missing or something like
that...

Also note I am using the latest BK as pulled about an hour ago.  I don't
know how old the snapshot you are using is in comparison.  Lots of UML
changes were pulled in by my pull...

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-08 10:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-08 10:09 Anton Altaparmakov
2005-02-08 10:22 ` Blaisorblade
2005-02-08 10:40   ` Anton Altaparmakov [this message]
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       ` 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=1107859254.582.4.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

Powered by JetHome