From: John Snow <jsnow@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] make distclean can fail do to a configuration check
Date: Mon, 29 Feb 2016 11:49:32 -0500 [thread overview]
Message-ID: <56D4769C.5080808@redhat.com> (raw)
In-Reply-To: <20160214071711.GD31933@ad.usersys.redhat.com>
On 02/14/2016 02:17 AM, Fam Zheng wrote:
> On Wed, 02/10 14:28, John Snow wrote:
>> Stuff like this:
>>
>>> ~/s/q/b/git> make distclean
>>> config-host.mak is out-of-date, running configure
>>>
>>> ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T.
>>> You probably need to set PKG_CONFIG_LIBDIR
>>> to point to the right pkg-config files for your
>>> build target
>>>
>>> Makefile:35: recipe for target 'config-host.mak' failed
>>> make: *** [config-host.mak] Error 1`
>>
>> is obnoxious. We had patches from Fam to allow some targets to bypass
>> the configuration check, did those die? Did we not want them for some
>> reason?
>
> What are your preceding commands? I have a clean checkout here (git clean -dfx)
> and "make distclean" works for me.
>
> Fam
>
This is due to the new glib-version-detection code that was checked in.
I had a configuration using clang, which does not appear to support the
mechanisms that are being used to tell what version of glib is being
linked against.
Practical upshot is that I can't even clean my clang configuration
because our makefile insists on re-configuring before it tries to clean.
Fam, didn't you have patches to allow e.g. cleans and "make tags" and so
on without re-incurring a full reconfiguration?
--js
next prev parent reply other threads:[~2016-02-29 16:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 19:28 [Qemu-devel] make distclean can fail do to a configuration check John Snow
2016-02-14 7:17 ` Fam Zheng
2016-02-29 16:49 ` John Snow [this message]
2016-02-29 16:54 ` Peter Maydell
2016-02-29 17:13 ` John Snow
2016-03-01 1:55 ` Fam Zheng
2016-03-01 15:47 ` John Snow
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=56D4769C.5080808@redhat.com \
--to=jsnow@redhat.com \
--cc=famz@redhat.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).