From: Blaisorblade <blaisorblade@yahoo.it>
To: Ian McDonald <imcdnzl@gmail.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] My personal -devel tree snapshotted out on my homepage!
Date: Thu, 14 Apr 2005 23:00:14 +0200 [thread overview]
Message-ID: <200504142300.14321.blaisorblade@yahoo.it> (raw)
In-Reply-To: <cbec11ac05041220314fa52041@mail.gmail.com>
On Wednesday 13 April 2005 05:31, Ian McDonald wrote:
> Comments below:
>
> On 13/04/05, Blaisorblade <blaisorblade@yahoo.it> wrote:
> > On Monday 11 April 2005 01:19, Ian McDonald wrote:
> > > With this patch applied to 2.6.11.7 it is my first kernel that
> > > compiles straight off :-)
> >
> > Ok, that's the -bs tree, not the one I announced here (the -devel one)
> > but it's ok anyway.
> >
> > > It does not apply one patch because it is already applied which is
> > > fine.
> >
> > Yes, I merged that, it's the va_copy fix.
>
> Sorry about that...
>
> > > I did a quick test against 2.6.12-rc2 and it didn't like that at all
> > > (many rejected patches). That is to be expected though as that is not
> > > the target but it does mean a reasonable amount of work ahead for
> > > Paolo :-(
> >
> > No; luckily, I'm mainly working on -rc2 and I've backported the needed
> > stuff to 2.6.11.
>
> Found the development snapshot and found the following problems:
> One patch did not apply. Documented in patch.out which is attached.
>
> Problem with arch/um/include/mode_kern.h as below
> In file included from arch/um/kernel/exec_kern.c:23:
> arch/um/include/mode_kern.h:12: unterminated string or character constant
> It doesn't like the #error on gcc 2.95.4 - if I do a remove of this
> line it compiles... will need a better fix than this though....
>
> Problem with arch/um/kernel/init_task.c as below
> arch/um/kernel/init_task.c:30: duplicate initializer
> arch/um/kernel/init_task.c:30: (near initialization for
> `init_task.thread.arch.debugregs')
> This is probably a duplication in initialisation of struct just like
> the problem we had with enum in syscalls and again due to gcc 2.95.4.
> I haven't tracked this one down fully yet but can if needed buy may
> take a while...
>
> I then hacked half that line out and got further compile errors in
> arch/um/kernel/process_kern.c as per attached file err.out. I then
> stopped as this looked a little more complicated...
>
> If you need any further information please tell me... I have also
> checked that 2.6.12-rc2 without the patch does compile and it does
> with the addition of the sed patch.
>
> If you want me to help I can apply the patches one by one but this
> will take some time...
Don't worry for now, that's the development tree and for now I'm not going to
merge it all of a sudden...
--
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
prev parent reply other threads:[~2005-04-14 20:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 18:20 [uml-devel] My personal -devel tree snapshotted out on my homepage! Blaisorblade
2005-04-10 23:19 ` Ian McDonald
2005-04-12 17:23 ` Blaisorblade
2005-04-13 3:31 ` Ian McDonald
2005-04-14 21:00 ` 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=200504142300.14321.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=imcdnzl@gmail.com \
--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