From: Phil Blundell <pb@pbcl.net>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Jack Mitchell <jmitchell@cbnl.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCHv4] libjson: update to 0.11 and rename to json-c
Date: Tue, 12 Nov 2013 23:37:25 +0000 [thread overview]
Message-ID: <1384299445.3828.31.camel@x121e.pbcl.net> (raw)
In-Reply-To: <1384295428.6460.71.camel@ted>
On Tue, 2013-11-12 at 22:30 +0000, Richard Purdie wrote:
> > + rm -rf ${S}/config.status ${S}/config.log ${S}/configure
> > ${S}/config.h ${S}/config.h.in~
>
> of these, config.status should get overwritten by gnu-configize
> (timestamp issue?),
I don't think gnu-configize overwrites config.status. Are you mixing it
up with config.sub?
> Equally, if you were doing out of tree builds, autoconf might detect
> that and error, maybe on the presence of config.log or config.h?
The "already configured" error is triggered by the existence of
${S}/config.status. So yes, this seems like a plausible theory.
p.
prev parent reply other threads:[~2013-11-12 22:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 15:59 [PATCHv4] libjson: update to 0.11 and rename to json-c Jack Mitchell
2013-11-08 0:47 ` Saul Wold
2013-11-11 19:13 ` Jack Mitchell
2013-11-12 20:58 ` Saul Wold
2013-11-12 22:30 ` Richard Purdie
2013-11-12 23:37 ` Phil Blundell [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=1384299445.3828.31.camel@x121e.pbcl.net \
--to=pb@pbcl.net \
--cc=jmitchell@cbnl.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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