From: Mark Hatle <mark.hatle@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>,
"Jérémy Rosen" <jeremy.rosen@smile.fr>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/8] [rpm] force a configure before make distclean
Date: Tue, 23 Aug 2016 12:16:55 -0500 [thread overview]
Message-ID: <ff5fb210-3bed-d6e7-8c07-6c3a9079c90b@windriver.com> (raw)
In-Reply-To: <CAJTo0LbHr7Bi20zYEG5+1383UkSb8=YmKATxOoP57DO-ZKX1Aw@mail.gmail.com>
On 8/23/16 11:54 AM, Burton, Ross wrote:
>
> On 23 August 2016 at 08:25, Jérémy Rosen <jeremy.rosen@smile.fr
> <mailto:jeremy.rosen@smile.fr>> wrote:
>
> - ( cd ${S}/syck ; set +e ; rm -- -l* ; make distclean ) || :
> + ( cd ${S}/syck ; set +e ; rm -- -l* ; ./configure ; make distclean )
> || :
>
>
> Running configure without all the options it needs to actually work just so that
> distclean works in a subbuild that shouldn't be breaking on rebuilds because we
> have out of tree builds scares me a little.
>
> Mark, you added this line, can you remember what it was for?
The syck version can be preconfigured, and if it is -- it's wrong.
The 'set +e' is specifically in there to ALLOW it to fail.
If it is configured, we much remove the junk and clean it.. if it's not been
configured, we ignore the make distclean failure.
So I'm not sure why it is necessary to make the change. 'Failure is permitted',
and make distclean shouldn't be using any 'BUILD_CC' values from prior builds...
since it's only wiping everything that MAY have been previously built and leaked
into the release archive.
--Mark
> Ross
next prev parent reply other threads:[~2016-08-23 17:16 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 7:25 [PATCH 0/8] Fix BUILD_* family of variables Jérémy Rosen
2016-08-23 7:25 ` [PATCH 1/8] [autotools] export CCLD_FOR_BUILD Jérémy Rosen
2016-08-24 0:50 ` Khem Raj
2016-08-24 11:05 ` Jérémy Rosen
2016-08-24 11:28 ` Jérémy Rosen
2016-08-24 19:56 ` Burton, Ross
2016-08-25 12:40 ` Jérémy Rosen
2016-08-25 13:27 ` Burton, Ross
2016-08-23 7:25 ` [PATCH 2/8] [cross] export CC family from BUILD_* for cross compilers Jérémy Rosen
2016-08-23 13:34 ` Peter Kjellerstedt
2016-08-23 14:46 ` Burton, Ross
2016-08-23 14:49 ` Jérémy Rosen
2016-08-23 7:25 ` [PATCH 3/8] [rpm] force a configure before make distclean Jérémy Rosen
2016-08-23 16:54 ` Burton, Ross
2016-08-23 17:16 ` Mark Hatle [this message]
2016-08-24 7:44 ` Jérémy Rosen
2016-08-24 14:13 ` Mark Hatle
2016-08-24 14:17 ` Jérémy Rosen
2016-08-24 14:42 ` Mark Hatle
2016-08-23 7:25 ` [PATCH 4/8] [linux-yocto] allow overriding compiler name in KConfig Jérémy Rosen
2016-08-23 13:36 ` Bruce Ashfield
2016-08-23 13:41 ` Bruce Ashfield
2016-08-23 13:48 ` Jérémy Rosen
2016-08-23 13:43 ` Jérémy Rosen
2016-08-23 7:25 ` [PATCH 5/8] [linux-libc-headers] " Jérémy Rosen
2016-08-23 13:39 ` Bruce Ashfield
2016-08-24 1:06 ` Khem Raj
2016-08-24 7:45 ` Jérémy Rosen
2016-08-23 7:25 ` [PATCH 6/8] [busybox] " Jérémy Rosen
2016-08-23 7:25 ` [PATCH 7/8] [sanity] fix hardcoded references to gcc Jérémy Rosen
2016-08-23 14:53 ` Burton, Ross
2016-08-23 15:11 ` Burton, Ross
2016-08-23 15:40 ` Jérémy Rosen
2016-08-24 7:47 ` Jérémy Rosen
2016-08-23 7:25 ` [PATCH 8/8] [glibc] remove hard-coded reference to gcc -E Jérémy Rosen
2016-08-23 14:03 ` Burton, Ross
2016-08-23 14:04 ` Jérémy Rosen
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=ff5fb210-3bed-d6e7-8c07-6c3a9079c90b@windriver.com \
--to=mark.hatle@windriver.com \
--cc=jeremy.rosen@smile.fr \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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