Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] BINFMT_FLAT_SHARED: is not really shared for buildroot purposes
Date: Fri, 27 Mar 2015 22:07:29 +0100	[thread overview]
Message-ID: <20150327220729.38caa8d1@free-electrons.com> (raw)
In-Reply-To: <1427489707-22707-1-git-send-email-arnout@mind.be>

Dear Arnout Vandecappelle (Essensium/Mind),

On Fri, 27 Mar 2015 21:55:07 +0100, Arnout Vandecappelle
(Essensium/Mind) wrote:

> diff --git a/docs/manual/adding-packages-generic.txt b/docs/manual/adding-packages-generic.txt
> index b6615ce..7508cfa 100644
> --- a/docs/manual/adding-packages-generic.txt
> +++ b/docs/manual/adding-packages-generic.txt
> @@ -208,8 +208,9 @@ information is (assuming the package name is +libfoo+) :
>    which Buildroot will use to download the tarball from
>    +LIBFOO_SITE+. If +HOST_LIBFOO_SOURCE+ is not specified, it defaults
>    to +LIBFOO_SOURCE+. If none are specified, then the value is assumed
> -  to be +libfoo-$(LIBFOO_VERSION).tar.gz+. + Example: +LIBFOO_SOURCE =
> -  foobar-$(LIBFOO_VERSION).tar.bz2+
> +  to be +libfoo-$(LIBFOO_VERSION).tar.gz+.
> +  +
> +  Example: +LIBFOO_SOURCE = foobar-$(LIBFOO_VERSION).tar.bz2+
>  
>  * +LIBFOO_PATCH+ may contain a space-separated list of patch file
>    names, that Buildroot will download and apply to the package source

Probably this part was not meant to be part of the patch, right? :-)

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2015-03-27 21:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27 20:55 [Buildroot] [PATCH] BINFMT_FLAT_SHARED: is not really shared for buildroot purposes Arnout Vandecappelle
2015-03-27 21:07 ` Thomas Petazzoni [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=20150327220729.38caa8d1@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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