linux-um archives
 help / color / mirror / Atom feed
From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: Testing GCOV handling in -bk
Date: Mon, 21 Mar 2005 10:49:49 +0000	[thread overview]
Message-ID: <1111402190.24494.12.camel@imp.csi.cam.ac.uk> (raw)
In-Reply-To: <200503201242.23591.blaisorblade@yahoo.it>

On Sun, 2005-03-20 at 12:42 +0100, Blaisorblade wrote:
> Anton, would you test the current -bk tree for the CONFIG_GCOV problem and the 
> patch I and Jeff put together?
> 
> http://user-mode-linux.sourceforge.net/work/current/2.6/2.6.11-bk8/patches/weak_gcov_init
> 
> The above should fix the situation for you... for real 3.4 Gcc, however, the 
> problems are bigger because it also requires to change link flags (and this 
> interferes with some executables we build). I also get a link failure on 
> __bb_fork_<something>..., which I haven't been able to solve until now.

I would test it but UML in current -BK doesn't build at all.  It stops
with:

  CC      kernel/signal.o
kernel/signal.c: In function `get_signal_to_deliver':
kernel/signal.c:1849: error: structure has no member named `eflags'
kernel/signal.c:1849: error: `TF_MASK' undeclared (first use in this
function)
kernel/signal.c:1849: error: (Each undeclared identifier is reported
only once
kernel/signal.c:1849: error: for each function it appears in.)
make[1]: *** [kernel/signal.o] Error 1
make: *** [kernel] Error 2

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/



-------------------------------------------------------
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

  reply	other threads:[~2005-03-21 10:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-20 11:42 [uml-devel] Testing GCOV handling in -bk Blaisorblade
2005-03-21 10:49 ` Anton Altaparmakov [this message]
2005-03-22 19:37   ` [uml-devel] " 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=1111402190.24494.12.camel@imp.csi.cam.ac.uk \
    --to=aia21@cam.ac.uk \
    --cc=blaisorblade@yahoo.it \
    --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