Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] doc: add libtool issue as Know issues
Date: Mon, 15 Aug 2016 13:09:30 +0200	[thread overview]
Message-ID: <1471259370-2914-2-git-send-email-romain.naour@gmail.com> (raw)
In-Reply-To: <1471259370-2914-1-git-send-email-romain.naour@gmail.com>

Signed-off-by: Romain Naour <romain.naour@gmail.com>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Arnout Vandecappelle <arnout@mind.be>
---
 docs/manual/known-issues.txt     | 4 ++++
 support/legal-info/README.header | 3 +++
 2 files changed, 7 insertions(+)

diff --git a/docs/manual/known-issues.txt b/docs/manual/known-issues.txt
index acfe4ff..d89507e 100644
--- a/docs/manual/known-issues.txt
+++ b/docs/manual/known-issues.txt
@@ -33,3 +33,7 @@
 * The +prboom+ package triggers a compiler failure with the SuperH 4
   compiler from Sourcery CodeBench, version 2012.09.
 
+* [2016.08] The libtool patches are not listed as package patches due
+  to a technical issue. Thereby they are not taken into account by the
+  legal-info infra. This will be fixed in a follow up Buildroot
+  release.
diff --git a/support/legal-info/README.header b/support/legal-info/README.header
index 1f3524f..6ba8b56 100644
--- a/support/legal-info/README.header
+++ b/support/legal-info/README.header
@@ -20,6 +20,9 @@ This material is composed of the following items.
    with a file named 'series' that lists the patches in the order they were
    applied. Patches are under the same license as the files that they modify
    in the original package.
+   Note: Libtool patches from support/libtool/buildroot-libtool-v*..patch,
+   used by autotools based packages, have not been saved due to technical
+   limitations, you may need to collect it manually.
  * A manifest file listing the configured packages and related information.
  * The license text of the packages; they have been saved in the licenses/
    subdirectory.
-- 
2.5.5

  reply	other threads:[~2016-08-15 11:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-15 11:09 [Buildroot] [PATCH 1/2] core/pkg-autotools: don't use APPLY_PATCHES for libtool patches Romain Naour
2016-08-15 11:09 ` Romain Naour [this message]
2016-08-15 11:59   ` [Buildroot] [PATCH 2/2] doc: add libtool issue as Know issues Yann E. MORIN
2016-08-15 22:44   ` Arnout Vandecappelle
2016-08-17 10:09     ` Yann E. MORIN
2016-08-15 11:56 ` [Buildroot] [PATCH 1/2] core/pkg-autotools: don't use APPLY_PATCHES for libtool patches Yann E. MORIN
2016-08-15 22:18 ` Arnout Vandecappelle

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=1471259370-2914-2-git-send-email-romain.naour@gmail.com \
    --to=romain.naour@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox