From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Interaction between SITE_METHOD=LOCAL and .patch files
Date: Tue, 7 Feb 2017 17:55:23 +0100 [thread overview]
Message-ID: <0a532bbd-e625-a41e-ece3-6974bd63d4a2@mind.be> (raw)
In-Reply-To: <o7araj$clq$1@blaine.gmane.org>
On 06-02-17 22:54, Grant Edwards wrote:
> 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.
It does. The technical reason for that is that SITE_METHOD = local is
implemented using _OVERRIDE_SRCDIR, and for that we don't want to apply patches
because the typical use case is to build some different version to which the
patches wouldn't apply anyway.
Also, when you set SITE_METHOD = local, there should be no reason to apply
patches because you can just as well apply them in your custom tarball.
> 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?
Indeed, it should be documented. Care to send a patch?
Regards,
Arnout
>
> [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.]
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2017-02-07 16:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 21:54 [Buildroot] Interaction between SITE_METHOD=LOCAL and .patch files Grant Edwards
2017-02-07 16:55 ` Arnout Vandecappelle [this message]
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=0a532bbd-e625-a41e-ece3-6974bd63d4a2@mind.be \
--to=arnout@mind.be \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox