linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net,
	Ian McDonald <imcdnzl@gmail.com>
Cc: Rob Landley <rob@landley.net>
Subject: Re: BUG with proposed fix Re: [uml-devel] Can't compile under vanilla 2.6.11
Date: Fri, 8 Apr 2005 06:24:37 +0200	[thread overview]
Message-ID: <200504080624.38124.blaisorblade@yahoo.it> (raw)
In-Reply-To: <cbec11ac05040721047a6dea90@mail.gmail.com>

On Friday 08 April 2005 06:04, Ian McDonald wrote:
> On Mar 24, 2005 11:03 PM, Blaisorblade <blaisorblade@yahoo.it> wrote:
> > On Monday 21 March 2005 06:30, Ian McDonald wrote:
> > > The other problem with not linking va_copy has been resolved by
> > > changing to __va_copy in skas/uaccess.c. This seems to be a known
> > > problem with older compilers and there is a patch out there but not in
> > > 2.6.11 or by the looks of it 2.6.12 rc1 by my reading of the log (nor
> > > for one for my previous e-mail)
> >
> > Ok, I'm taking that patch and merging it in my tree and in 2.6.12. I hope
> > it can go also in 2.6.11.6 (or .7, whatever).
> >
> > --
> > Paolo Giarrusso, aka Blaisorblade
> > Linux registered user n. 292729
> > http://www.user-mode-linux.org/~blaisorblade
>
> Here is an update:
> 2.6.12-rc2 has both va_copy patch and syscall patch and works for me
> once a patch is applied to arch/um/kernel/Makefile for some sed syntax
> 2.6.11.7 has va_copy patch only and works for me once I apply the
> syscall patch that I started and Paolo made much better.
I've sent it for merging, and I hope it will be in .8.
> Environment is Debian Woody, gcc 2.95.4, sed 3.02
>
> Thanks again for all involved in helping me to this state.
I'll put these changes also in the -bs tree. Actually, -bs1 should work for 
you because has the syscall and va_copy changes; -bb2 does not work because I 
merged the sed usage which bites you.

I'll now merge the sed fix for -bs3.
-- 
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

      reply	other threads:[~2005-04-08  4:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-18  3:18 [uml-devel] Can't compile under vanilla 2.6.11 Ian McDonald
2005-03-18  3:40 ` Rob Landley
2005-03-18  6:34   ` Ian McDonald
2005-03-18 23:42 ` Rob Landley
2005-03-18 23:43 ` Rob Landley
2005-03-19 21:31   ` [uml-devel] Running JDK1.5 Maxes Out CPU Peter
2005-03-21  4:43   ` BUG with proposed fix Re: [uml-devel] Can't compile under vanilla 2.6.11 Ian McDonald
2005-03-21  5:13     ` [uml-devel] 2.4 do_mmap_pgoff compile problem Peter
2005-03-22 17:50       ` Blaisorblade
2005-03-21  5:30     ` BUG with proposed fix Re: [uml-devel] Can't compile under vanilla 2.6.11 Ian McDonald
2005-03-24 11:03       ` Blaisorblade
2005-04-08  4:04         ` Ian McDonald
2005-04-08  4:24           ` 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=200504080624.38124.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=imcdnzl@gmail.com \
    --cc=rob@landley.net \
    --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