From: Ian McDonald <imcdnzl@gmail.com>
To: Rob Landley <rob@landley.net>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: BUG with proposed fix Re: [uml-devel] Can't compile under vanilla 2.6.11
Date: Mon, 21 Mar 2005 17:30:34 +1200 [thread overview]
Message-ID: <cbec11ac05032021301a9083f7@mail.gmail.com> (raw)
In-Reply-To: <cbec11ac05032020433867d95e@mail.gmail.com>
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)
On Mon, 21 Mar 2005 16:43:54 +1200, Ian McDonald <imcdnzl@gmail.com> wrote:
> OK after much further investigation, redownloading of source
> (2.6.11.4) and looking at what you have said I know why it is
> breaking....
>
> I had assumed (wrongly of course) that ARCH_SYSCALLS was a one line
> symbol definition but it is much more than this.
>
> The problem occurs because in both
> arch/um/include/sysdep-i386/syscalls.h and in
> arch/um/kernel/sys_call_table.c a number of the elements are defined
> in BOTH files.
>
> I presume the reason why this doesn't break others systems is that
> they are not using the same version of gcc as me (2.95.4). I would
> guess that with a later gcc in an enum you can redefine an element and
> it doesn't complain...
>
> Anyway I believe the proper fix is to delete the lines from
> arch/um/kernel/sys_call_table.c and here is a patch to do that:
>
> 255d254
> < [ __NR_statfs64 ] = (syscall_handler_t *) sys_statfs64,
> 258,260d256
> < [ __NR_utimes ] = (syscall_handler_t *) sys_utimes,
> < [ __NR_fadvise64_64 ] = (syscall_handler_t *) sys_fadvise64_64,
> < [ __NR_vserver ] = (syscall_handler_t *) sys_vserver,
>
> Can somebody verify that and if correct submit to whoever (this is my
> first ever attempt at fixing something in the kernel so not quite sure
> what to do next!!)
>
> Regards,
>
> Ian
>
> PS still have some linking issues and I will report on them as I work
> out why....
>
> On Fri, 18 Mar 2005 18:43:05 -0500, Rob Landley <rob@landley.net> wrote:
> > Ah, nevermind. Check out Anton's message. You were using a -bk snapshot
> > rather than the officially 2.6.11 release, I take it?
> >
> > Rob
> >
>
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-03-21 5:30 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 ` Ian McDonald [this message]
2005-03-24 11:03 ` BUG with proposed fix Re: [uml-devel] Can't compile under vanilla 2.6.11 Blaisorblade
2005-04-08 4:04 ` Ian McDonald
2005-04-08 4:24 ` 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=cbec11ac05032021301a9083f7@mail.gmail.com \
--to=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