Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: Native patch appears broken on Fedora 21
Date: Wed, 28 Oct 2015 19:06:16 -0500	[thread overview]
Message-ID: <563162F8.3050102@windriver.com> (raw)
In-Reply-To: <56315EE5.3070100@balister.org>

On 10/28/15 6:48 PM, Philip Balister wrote:
> I've been chasing an annoying build failure in a clients u-boot recipe.
> 
> One of the patches adds an executable python script to the u-boot tools
> directory and runs it as part of the build.
> 
> With recent master on a Fedora 20 system, it works.
> 
> Recent master on Fedora 21, the script does not end up marked as
> executable so build fails.
> 
> After much thinking and poking and remembering how this is supposed to
> work I get the brilliant idea to copy the patch binary from the F20
> machine to the F21 machine. Problem goes away.
> 
> Something is weird here, I can't believe this is the only patch in the
> system that marks a file executable and runs it, but maybe it is.

Most of the time I patch things in, and then run a chmod to ensure it's
executable.  Then I'm sure it will work.  (Patch doing mode changes is 'fairly
new'...)

--Mark

> Versions of patch.
> 
> F20 GNU patch 2.7.1
> F21 GNU patch 2.7.5
> 
> Looking at the patch changelog didn't help.
> 
> Anyone have any ideas what to do about this?
> 
> Philip
> 



      reply	other threads:[~2015-10-29  0:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-28 23:48 Native patch appears broken on Fedora 21 Philip Balister
2015-10-29  0:06 ` Mark Hatle [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=563162F8.3050102@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.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