From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next 0/2] Per-package folder fixes
Date: Thu, 15 Nov 2018 16:21:05 +0100 [thread overview]
Message-ID: <20181115152107.5834-1-thomas.petazzoni@bootlin.com> (raw)
Hello,
Here are two patches that illustrate the kind of issue that one can
face with some packages when using per-package folders.
The commit log explain in further details the problems.
Thomas
Thomas Petazzoni (2):
package/apr-util: fix build with per-package folders
package/apache: add patch to fix per-package folder build
...in-handle-separate-APR_INCLUDE_DIR-A.patch | 47 +++++++++++++++++++
package/apr-util/apr-util.mk | 9 ++++
2 files changed, 56 insertions(+)
create mode 100644 package/apache/0003-server-Makefile.in-handle-separate-APR_INCLUDE_DIR-A.patch
--
2.19.1
next reply other threads:[~2018-11-15 15:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 15:21 Thomas Petazzoni [this message]
2018-11-15 15:21 ` [Buildroot] [PATCH next 1/2] package/apr-util: fix build with per-package folders Thomas Petazzoni
2018-11-15 20:13 ` Yann E. MORIN
2018-11-20 15:56 ` Thomas Petazzoni
2018-11-15 15:21 ` [Buildroot] [PATCH next 2/2] package/apache: add patch to fix per-package folder build Thomas Petazzoni
2018-11-15 20:45 ` Yann E. MORIN
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=20181115152107.5834-1-thomas.petazzoni@bootlin.com \
--to=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox