From: Jamie Lokier <jamie@shareable.org>
To: Riku Voipio <riku.voipio@iki.fi>
Cc: qemu-devel@nongnu.org, Nathan Froyd <froydnj@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH] linux-user: Added IP_ADD_MEMBERSHIP/IP_DROP_MEMBERSHIP flags to setsockopt
Date: Thu, 30 Apr 2009 03:41:02 +0100 [thread overview]
Message-ID: <20090430024102.GA3011@shareable.org> (raw)
In-Reply-To: <20090429214124.GA32434@kos.to>
Riku Voipio wrote:
> On Wed, Apr 29, 2009 at 10:00:18PM +0100, Jamie Lokier wrote:
> > Riku Voipio wrote:
> > > On Wed, Apr 29, 2009 at 09:35:52PM +0100, Jamie Lokier wrote:
> > > > Riku Voipio wrote:
> > > > > These are defined in include/linux/in.h so they should be same on all archs?
> > >
> > > > But what if you're compiling for a non-Linux host?
> > >
> > > Generally speaking if you comple Qemu Linux-user on a non-Linux host you
> > > just fail. With or without this patch.
>
> > Oh. Are non-Linux hosts officially not supported, or is this just a
> > matter of some things being broken?
>
> It is not officially supported. There are just too many places in the
> current linux-user code that expect a linux host. Thou there has been
> interest in working those bits to be more generic recently. recently.
If there's real interest in working those bits for other hosts,
*new* bits should use TARGET_ constants to avoid making life even
harder when it comes to finding places where'll they need to be
changed to TARGET_ later.
-- Jamie
next prev parent reply other threads:[~2009-04-30 2:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-25 21:30 [Qemu-devel] [PATCH] linux-user: Added IP_ADD_MEMBERSHIP/IP_DROP_MEMBERSHIP flags to setsockopt Lionel Landwerlin
2009-04-27 17:21 ` Nathan Froyd
2009-04-27 18:05 ` Lionel Landwerlin
2009-04-29 18:00 ` Riku Voipio
2009-04-29 20:35 ` Jamie Lokier
2009-04-29 20:43 ` Riku Voipio
2009-04-29 21:00 ` Jamie Lokier
2009-04-29 21:41 ` Riku Voipio
2009-04-30 2:41 ` Jamie Lokier [this message]
2009-04-29 23:08 ` Lionel Landwerlin
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=20090430024102.GA3011@shareable.org \
--to=jamie@shareable.org \
--cc=froydnj@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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;
as well as URLs for NNTP newsgroup(s).