From: Christopher Friedt <chrisfriedt@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Fam Zheng <famz@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	QEMU Trivial <qemu-trivial@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	G 3 <programmingkidx@gmail.com>
Subject: Re: [Qemu-devel] [PATCH 2/2] Remove unnecessary CONFIG_EVENTFD preprocessor conditional to satisfy link
Date: Mon, 2 May 2016 21:25:26 -0400	[thread overview]
Message-ID: <CAF4BF-RzconSOm++Ey79FO2wm2JSK=PYV5UNnnjZvEyOkf3tgA@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA_kViE8oaiPE9SNGSXBRo4vocKuZXQuruyRULrjy9id4A@mail.gmail.com>
On Mon, May 2, 2016 at 9:18 PM, Peter Maydell <peter.maydell@linaro.org> wrote:
> On 3 May 2016 at 02:14, Christopher Friedt <chrisfriedt@gmail.com> wrote:
>> On Mon, May 2, 2016 at 9:01 PM, Peter Maydell <peter.maydell@linaro.org> wrote:
>>> [ccing somebody else who ran into this, since I've figured out why.]
>>>
>>> On 3 May 2016 at 01:47, Christopher Friedt <chrisfriedt@gmail.com> wrote:
>>>> The file ivshmem.c unconditionally references event_notifier_init_fd()
>>>> in util/event_notifier-posix.c, even if CONFIG_EVENTFD is not defined.
>>>
>>> Yes, but ivshmem.c is only built if CONFIG_IVSHMEM, and
>>> CONFIG_IVSHMEM is set (in default-configs/pci.mak) to CONFIG_EVENTFD.
>>> So if CONFIG_EVENTFD is not defined then we should never build ivshmem.o.
>>>
>>> The problem here is that you've run into a bug in QEMU's makefiles,
>>
>> That would explain things.
> Hmm. (Is it set the same for every config-devices.mak for
> every target you're trying to build?)
Ack - too late! I manually removed all of the *-softmmu/ directories
after doing a make clean, because they were still hanging around.
Rebuilding worked fine without PATCH 2/2.
Thanks!
next prev parent reply	other threads:[~2016-05-03  1:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-03  0:47 [Qemu-devel] [PATCH 0/2] Resolve link errors on Mac OS X Christopher Friedt
2016-05-03  0:47 ` [Qemu-devel] [PATCH 1/2] Use libtool instead of ar to create static libraries on Darwin Christopher Friedt
2016-05-03  0:53   ` Peter Maydell
2016-05-03  1:08     ` Christopher Friedt
2016-05-03  1:04   ` Fam Zheng
2016-05-03  1:08     ` Christopher Friedt
2016-05-06 19:07   ` Michael Tokarev
2016-05-06 22:26     ` Peter Maydell
2016-05-03  0:47 ` [Qemu-devel] [PATCH 2/2] Remove unnecessary CONFIG_EVENTFD preprocessor conditional to satisfy link Christopher Friedt
2016-05-03  1:01   ` Peter Maydell
2016-05-03  1:14     ` Christopher Friedt
2016-05-03  1:18       ` Peter Maydell
2016-05-03  1:25         ` Christopher Friedt [this message]
2016-05-03  1:27           ` Peter Maydell
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='CAF4BF-RzconSOm++Ey79FO2wm2JSK=PYV5UNnnjZvEyOkf3tgA@mail.gmail.com' \
    --to=chrisfriedt@gmail.com \
    --cc=famz@redhat.com \
    --cc=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=programmingkidx@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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).