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

On Monday 21 March 2005 11:49, Anton Altaparmakov wrote:
> 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/patche
> >s/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
Ok, watch the patches I'm sending now. The one titled "uml: fix compile" fix 
the above problem, while the one named "uml: real fix for __gcov_init 
symbols" is what I'm merging for this problem (from your results I guess it 
should work well for you too).
-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade





-------------------------------------------------------
This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
for the chance to win $25,000 and application distribution. Enter today at
http://ads.osdn.com/?ad_id=6882&alloc_id=15148&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-22 19:42 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 ` [uml-devel] " Anton Altaparmakov
2005-03-22 19:37   ` Blaisorblade [this message]

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