public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: "Jérémy Rosen" <jeremy.rosen@smile.fr>,
	"Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/8] [rpm] force a configure before make distclean
Date: Wed, 24 Aug 2016 09:42:35 -0500	[thread overview]
Message-ID: <1e3cae90-026d-d2b8-bf7e-a7d2be57804b@windriver.com> (raw)
In-Reply-To: <a5c693a1-42a3-2234-291c-eef54f9a4358@smile.fr>

On 8/24/16 9:17 AM, Jérémy Rosen wrote:
> 
> 
> On 24/08/2016 16:13, Mark Hatle wrote:
>>
>> Make often has a rule looking at the time stamp of specific files and re-running
>> specific autotools if they are 'out of date'.  That COULD be the cause of the
>> errant call to gcc?
> that would make sense...
>>
>> I have not observed the above occurring -- but the key thing is that syck needs
>> to be cleaned of the generated files.  We don't want to run any host commands
>> other then clean it.
>>
>> If you have to replace it with something else, you will need to identify all of
>> the files that need to be cleaned and manually remove them avoiding the
>> distclean call.
>>
>> Easiest way to do that.... extract the source for syck, back it up, run the make
>> distclean.. compare the difference and use that list as a replacement 'cleanup'
>> command.
> 
> That wouldn't be very robust to future change in syck, i'm afraid... but 
> i'll have a look.

There is nothing robust about this change for future work.  Future versions will
have to do the work in a different way -- and hopefully won't have pre-built
crap slipped into the download that we have to cleanup.

So I have no concern about future proofing this, as I know the next integration
-will- be different in this case.

--Mark

>>
>> --Mark
>>
>>
> 



  reply	other threads:[~2016-08-24 14:42 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
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 [this message]
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=1e3cae90-026d-d2b8-bf7e-a7d2be57804b@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