From: Dave Feustel <dfeustel@verizon.net>
To: qemu-devel@nongnu.org
Cc: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] qemu and svn
Date: Tue, 15 Nov 2005 09:05:51 -0500 [thread overview]
Message-ID: <200511150905.51691.dfeustel@verizon.net> (raw)
In-Reply-To: <200511141902.24997.dfeustel@verizon.net>
On Monday 14 November 2005 19:02, Dave Feustel wrote:
> These errors are new. I don't yet understand why they are happening.
My mistake. I saw exactly these same errors while porting PETSc and MPICH2 to OpenBSD
and didn't realize until this morning that they were now occuring on a *different* project..
It looks like OpenBSD needs to add some header files to /usr/include.
I apologise for the noise I generated in my confusion.
Dave
--
Switch to Secure OpenBSD with a KDE desktop!!!
NOW with Virtual PC OS support via QEMU and
Beowulf clustering using PETSc and MPICH2!
prev parent reply other threads:[~2005-11-15 14:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 23:05 [Qemu-devel] qemu and svn Dave Feustel
2005-11-14 23:13 ` Paul Brook
2005-11-14 23:32 ` Dave Feustel
2005-11-15 0:02 ` Dave Feustel
2005-11-15 14:05 ` Dave Feustel [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=200511150905.51691.dfeustel@verizon.net \
--to=dfeustel@verizon.net \
--cc=dfeustel@mindspring.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
/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).