From: Luiz Capitulino <lcapitulino@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, "Michael Roth" <mdroth@linux.vnet.ibm.com>,
"dunrong huang" <riegamaths@gmail.com>,
agraf@suse.de, qemu@buildbot.b1-systems.de, gollub@b1-systems.de,
"Eric Blake" <eblake@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] buildbot failure in qemu on default_openbsd_current
Date: Wed, 23 May 2012 13:11:41 -0300 [thread overview]
Message-ID: <20120523131141.42d4fa70@doriath.home> (raw)
In-Reply-To: <4FBD0AFA.7010607@redhat.com>
On Wed, 23 May 2012 18:06:18 +0200
Paolo Bonzini <pbonzini@redhat.com> wrote:
> Il 23/05/2012 17:57, Luiz Capitulino ha scritto:
> > On Wed, 23 May 2012 11:35:49 -0300
> > Luiz Capitulino <lcapitulino@redhat.com> wrote:
> >
> >>> Maybe we need a patch to declare environ for openbsd
> >>
> >> Yes, I have the patch already but am installing openbsd on a VM to test it.
> >
> > I'm getting lots of make errors on openbsd 4.9:
> >
> > "Makefile", line 7: Missing dependency operator
> > "/root/qemu.a/rules.mak", line 20: Missing dependency operator
> > "/root/qemu.a/rules.mak", line 23: Need an operator
> > "/root/qemu.a/rules.mak", line 26: Need an operator
> > "Makefile", line 15: Need an operator
> > "Makefile", line 19: Need an operator
> > "Makefile", line 22: Missing dependency operator
> > "Makefile", line 24: Need an operator
> > Bad modifier: $(SRC_PATH)/hw)
> >
> > Bad modifier: $(SRC_PATH)/hw)
> >
> > "Makefile", line 36: Need an operator
> >
> > Anyone knows what I did wrong? Or, if anybody could test the attached fix...
>
> Probably you need to install gnumake.
Yeah, Andreas helped by irc, but now I get zillions of -Wno-redundant-decls errors:
In file included from /root/qemu.a/qemu-common.h:33,
from /root/qemu.a/module.c:16:
/usr//include/unistd.h:99: warning: redundant redeclaration of 'lseek'
/usr//include/sys/types.h:210: warning: previous declaration of 'lseek' was here
/usr//include/unistd.h:138: warning: redundant redeclaration of 'ftruncate'
/usr//include/sys/types.h:211: warning: previous declaration of 'ftruncate' was here
I've removed -Wno-redundant-decls and I finally get the environ build error,
but I wonder why build bot doesn't get it.
next prev parent reply other threads:[~2012-05-23 16:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 23:09 [Qemu-devel] buildbot failure in qemu on default_openbsd_current qemu
2012-05-22 23:41 ` Andreas Färber
2012-05-23 2:35 ` dunrong huang
2012-05-23 13:39 ` Luiz Capitulino
2012-05-23 14:33 ` dunrong huang
2012-05-23 14:35 ` Luiz Capitulino
2012-05-23 15:57 ` Luiz Capitulino
2012-05-23 16:01 ` Eric Blake
2012-05-23 18:46 ` Luiz Capitulino
2012-05-23 16:06 ` Paolo Bonzini
2012-05-23 16:11 ` Luiz Capitulino [this message]
2012-05-23 16:22 ` Michael Roth
-- strict thread matches above, loose matches on Subject: below --
2012-09-15 0:55 qemu
2012-08-15 23:06 qemu
2012-07-28 23:09 qemu
2012-07-19 23:14 qemu
2012-07-17 23:08 qemu
2012-06-09 0:31 qemu
2012-06-10 16:01 ` Paolo Bonzini
2012-06-10 20:36 ` Blue Swirl
2012-03-01 0:08 qemu
2012-02-04 0:07 qemu
2011-10-03 23:12 qemu
2011-09-20 23:05 qemu
2011-08-14 23:11 qemu
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=20120523131141.42d4fa70@doriath.home \
--to=lcapitulino@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=eblake@redhat.com \
--cc=gollub@b1-systems.de \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu@buildbot.b1-systems.de \
--cc=riegamaths@gmail.com \
/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).