All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Interaction between SITE_METHOD=LOCAL and .patch files
Date: Mon, 6 Feb 2017 21:54:27 +0000 (UTC)	[thread overview]
Message-ID: <o7araj$clq$1@blaine.gmane.org> (raw)

I've been chasing a bug in a package for a couple days, and have been
baffled because the executable failed with segfault when it was built
from a local package.tar.gz file located in thepackage directory
(where the package.mk file is).  However, if I unpack package.tar.gz
and then set the SITE_METHOD to LOCAL, the executable works fine.

After comparing build trees that worked with build trees that failed,
I finallythat setting SITE_METHOD = LOCAL prevents the application of
the .patch files present in the package directory. 

I don't find this behavior documented anywhere.  The description of
SITE_METHOD only says it affects how the sources are fetched.  It
doesn't say anything about it controlling whether or not patches are
applied.  Is it interaction intentional, or is it a bug?

[FWIW, the package in question is the most recent version of the ipkg
package, and the 0001-fix-musl-build.patch is what breaks it.  Since
that package has already been removed, I won't bother to file a bug
report.]

-- 
Grant Edwards               grant.b.edwards        Yow! Are we wet yet?
                                  at               
                              gmail.com            

             reply	other threads:[~2017-02-06 21:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-06 21:54 Grant Edwards [this message]
2017-02-07 16:55 ` [Buildroot] Interaction between SITE_METHOD=LOCAL and .patch files Arnout Vandecappelle
2017-02-07 17:18   ` Grant Edwards
2017-02-07 17:37     ` Grant Edwards
2017-02-07 19:47       ` Peter Korsgaard
2017-02-08  9:02         ` Thomas Petazzoni
2017-02-08  9:01     ` Thomas Petazzoni

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='o7araj$clq$1@blaine.gmane.org' \
    --to=grant.b.edwards@gmail.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.