qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Stefan Stonjek <s.stonjek1@physics.ox.ac.uk>
Subject: Re: [Qemu-devel] SO_BSDCOMPAT in qemu's syscall.c
Date: Thu, 10 Mar 2005 02:31:25 +0000	[thread overview]
Message-ID: <200503100231.27250.paul@codesourcery.com> (raw)
In-Reply-To: <422FA690.40502@physics.ox.ac.uk>

On Thursday 10 March 2005 01:44, Stefan Stonjek wrote:
> Hello,
>
> I just tried to compile qemu 0.6.1 on SuSE Linux 9.2. Since a standard
> "configure ; make ; make install" failed, I checked the reason.
>
> The problem was that line 580 of syscall.c refers to a preprocessor
> constant SO_BSDCOMPAT. 

This has already been fixed in CVS.

Paul

      reply	other threads:[~2005-03-10  2:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-10  1:44 [Qemu-devel] SO_BSDCOMPAT in qemu's syscall.c Stefan Stonjek
2005-03-10  2:31 ` Paul Brook [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=200503100231.27250.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    --cc=s.stonjek1@physics.ox.ac.uk \
    /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).