From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-user@lists.sourceforge.net,
user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: [uml-user] SKAS-V8, UML/2.4.27-bs2-pre7 released, start of work on SKAS/x86-64
Date: Thu, 24 Mar 2005 03:46:33 +0100 [thread overview]
Message-ID: <200503240346.35907.blaisorblade@yahoo.it> (raw)
In-Reply-To: <200503240335.15219.blaisorblade@yahoo.it>
On Thursday 24 March 2005 03:35, Blaisorblade wrote:
> Ok, I've put on the site the announcements of SKAS-v8 (which is identical
> to -rc5, I just need to update the tarballs), of the test tree (very test)
> for UML/2.4.
It does not compile with GCC 3.4, but from what I see no 2.4.27 tree will
compile with that GCC, even for i386: it is stricter on attributes like
regparm and thus on FASTCALL, so he refuses this:
static FASTCALL(void reschedule_idle(struct task_struct * p));
static void reschedule_idle(struct task_struct * p)
because it says they are different declarations.
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
-------------------------------------------------------
This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005
Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows
Embedded(r) & Windows Mobile(tm) platforms, applications & content. Register
by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&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-03-24 2:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 2:35 [uml-devel] SKAS-V8, UML/2.4.27-bs2-pre7 released, start of work on SKAS/x86-64 Blaisorblade
2005-03-24 2:46 ` 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=200503240346.35907.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@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