* [Buildroot] [PATCH v2 1/3] core/pkg-autotools: don't use APPLY_PATCHES for libtool patches
@ 2016-08-17 16:01 Romain Naour
2016-08-17 16:01 ` [Buildroot] [PATCH v2 2/3] docs: update legal-notice.txt Romain Naour
` (2 more replies)
0 siblings, 3 replies; 9+ messages in thread
From: Romain Naour @ 2016-08-17 16:01 UTC (permalink / raw)
To: buildroot
Since [1] <package>-reconfigure target is broken.
$ make elementary-reconfigure
Applying buildroot-libtool-v2.4.4.patch using patch:
Error: duplicate filename 'buildroot-libtool-v2.4.4.patch'
Conflicting files are:
already applied: buildroot/support/libtool/buildroot-libtool-v2.4.4.patch
to be applied : buildroot/support/libtool/buildroot-libtool-v2.4.4.patch
When a package uses AUTORECONF, the libtool patch can be applied a
second time on the same ltmain.sh in the same directory as the
<package>-reconfigure target is called. This is not a problem since
autoreconf will overwrite the previously patched files. But with the
check introduced by [1], apply-patches.sh throw an error when the
package is reconfigured since the libtool patch is already present in
.applied_patches_list.
In addition to this, the .applied_patches_list file generated by
apply-patches.sh while patching ltmain.sh is not in the top-level
package source directory. Instead a duplicated .applied_patches_list
is generated beside the patched ltmain.sh which can be in a
subdirectory.
As noticed by Arnout Vandecappelle [2], the apply-patches.sh script
doesn't bring anything for the libtool patches.
"apply_patches.sh does the following:
* It handles directories -> not needed here.
* It handles compressed patches and tarballs -> not needed.
* It handles series files -> not needed.
* It handles errors in case of multiple patches -> not needed since
it's only one patch.
* It detects errors based on *.rej files -> not needed since it's only
a single patch so patch exit code is OK.
* It writes the patch list -> for libtool, this is quite silly because
it will be written in the directory where ltmain.sh is found, not in the
top-level directory, so you have these patch lists spread over the
source tree."
So use patch directly rather than apply-patches.
[1] 19241598147e7555dce40b6dd44b28ef22b67ed9
[2] http://lists.busybox.net/pipermail/buildroot/2016-August/169810.html
Signed-off-by: Romain Naour <romain.naour@gmail.com>
Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Tested-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Arnout Vandecappelle <arnout@mind.be>
---
v2: improve the commit log (Arnout)
---
package/pkg-autotools.mk | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/package/pkg-autotools.mk b/package/pkg-autotools.mk
index 75e2df0..d1cdb89 100644
--- a/package/pkg-autotools.mk
+++ b/package/pkg-autotools.mk
@@ -65,14 +65,14 @@ define LIBTOOL_PATCH_HOOK
ltmain_patchlevel=`sed -n '/^[ \t]*VERSION=/{s/^[ \t]*VERSION=//;p;q;}' $$i | \
sed -e 's/\([0-9]*\.[0-9]*\.*\)\([0-9]*\).*/\2/' -e 's/\"//'`; \
if test $${ltmain_version} = '1.5'; then \
- $(APPLY_PATCHES) $${i%/*} support/libtool buildroot-libtool-v1.5.patch; \
+ patch -i support/libtool/buildroot-libtool-v1.5.patch $${i}; \
elif test $${ltmain_version} = "2.2"; then\
- $(APPLY_PATCHES) $${i%/*} support/libtool buildroot-libtool-v2.2.patch; \
+ patch -i support/libtool/buildroot-libtool-v2.2.patch $${i}; \
elif test $${ltmain_version} = "2.4"; then\
if test $${ltmain_patchlevel:-0} -gt 2; then\
- $(APPLY_PATCHES) $${i%/*} support/libtool buildroot-libtool-v2.4.4.patch; \
+ patch -i support/libtool/buildroot-libtool-v2.4.4.patch $${i}; \
else \
- $(APPLY_PATCHES) $${i%/*} support/libtool buildroot-libtool-v2.4.patch; \
+ patch -i support/libtool/buildroot-libtool-v2.4.patch $${i}; \
fi \
fi \
done
--
2.5.5
^ permalink raw reply related [flat|nested] 9+ messages in thread
* [Buildroot] [PATCH v2 2/3] docs: update legal-notice.txt
2016-08-17 16:01 [Buildroot] [PATCH v2 1/3] core/pkg-autotools: don't use APPLY_PATCHES for libtool patches Romain Naour
@ 2016-08-17 16:01 ` Romain Naour
2016-08-17 17:19 ` Yann E. MORIN
2016-08-19 14:20 ` Thomas Petazzoni
2016-08-17 16:01 ` [Buildroot] [PATCH v2 3/3] docs: libtool patches are not handled by legal-info infrastructure Romain Naour
2016-08-18 21:59 ` [Buildroot] [PATCH v2 1/3] core/pkg-autotools: don't use APPLY_PATCHES for libtool patches Thomas Petazzoni
2 siblings, 2 replies; 9+ messages in thread
From: Romain Naour @ 2016-08-17 16:01 UTC (permalink / raw)
To: buildroot
Since 1273636fc686cd788b6de87be75dd0726cf8676c applied patches are also
saved.
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/legal-notice.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/manual/legal-notice.txt b/docs/manual/legal-notice.txt
index 0572dae..a4911f7 100644
--- a/docs/manual/legal-notice.txt
+++ b/docs/manual/legal-notice.txt
@@ -41,9 +41,9 @@ There you will find:
+host-sources/+ subdirectories for target and host packages respectively.
The source code for packages that set +<PKG>_REDISTRIBUTE = NO+ will not be
saved.
- Patches applied to some packages by Buildroot are distributed with the
- Buildroot sources and are not duplicated in the +sources/+ and +host-sources/+
- subdirectories.
+ Patches that were applied are also saved, along 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.
* A manifest file (one for host and one for target packages) listing the
configured packages, their version, license and related information.
Some of this information might not be defined in Buildroot; such items are
--
2.5.5
^ permalink raw reply related [flat|nested] 9+ messages in thread
* [Buildroot] [PATCH v2 3/3] docs: libtool patches are not handled by legal-info infrastructure.
2016-08-17 16:01 [Buildroot] [PATCH v2 1/3] core/pkg-autotools: don't use APPLY_PATCHES for libtool patches Romain Naour
2016-08-17 16:01 ` [Buildroot] [PATCH v2 2/3] docs: update legal-notice.txt Romain Naour
@ 2016-08-17 16:01 ` Romain Naour
2016-08-17 17:22 ` Yann E. MORIN
2016-08-19 21:34 ` Thomas Petazzoni
2016-08-18 21:59 ` [Buildroot] [PATCH v2 1/3] core/pkg-autotools: don't use APPLY_PATCHES for libtool patches Thomas Petazzoni
2 siblings, 2 replies; 9+ messages in thread
From: Romain Naour @ 2016-08-17 16:01 UTC (permalink / raw)
To: buildroot
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/legal-notice.txt | 4 ++++
support/legal-info/README.header | 4 ++++
2 files changed, 8 insertions(+)
diff --git a/docs/manual/legal-notice.txt b/docs/manual/legal-notice.txt
index a4911f7..fd1e5aa 100644
--- a/docs/manual/legal-notice.txt
+++ b/docs/manual/legal-notice.txt
@@ -44,6 +44,10 @@ There you will find:
Patches that were applied are also saved, along 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.
+ Note: Buildroot applies additional patches to Libtool scripts of
+ autotools-based packages. These patches can be found under +support/libtool+
+ in the buildroot source and are not saved with the package sources due to
+ technical limitations. You may need to collect them manually.
* A manifest file (one for host and one for target packages) listing the
configured packages, their version, license and related information.
Some of this information might not be defined in Buildroot; such items are
diff --git a/support/legal-info/README.header b/support/legal-info/README.header
index 1f3524f..ee34886 100644
--- a/support/legal-info/README.header
+++ b/support/legal-info/README.header
@@ -20,6 +20,10 @@ 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: Buildroot applies additional patches to Libtool scripts of
+ autotools-based packages. These patches can be found under support/libtool
+ in the buildroot source and are not saved with the package sources due to
+ technical limitations. You may need to collect them 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
^ permalink raw reply related [flat|nested] 9+ messages in thread
* [Buildroot] [PATCH v2 2/3] docs: update legal-notice.txt
2016-08-17 16:01 ` [Buildroot] [PATCH v2 2/3] docs: update legal-notice.txt Romain Naour
@ 2016-08-17 17:19 ` Yann E. MORIN
2016-08-19 14:20 ` Thomas Petazzoni
1 sibling, 0 replies; 9+ messages in thread
From: Yann E. MORIN @ 2016-08-17 17:19 UTC (permalink / raw)
To: buildroot
Romain, All,
On 2016-08-17 18:01 +0200, Romain Naour spake thusly:
> Since 1273636fc686cd788b6de87be75dd0726cf8676c applied patches are also
> saved.
>
> 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>
Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Regards,
Yann E. MORIN.
> ---
> docs/manual/legal-notice.txt | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/docs/manual/legal-notice.txt b/docs/manual/legal-notice.txt
> index 0572dae..a4911f7 100644
> --- a/docs/manual/legal-notice.txt
> +++ b/docs/manual/legal-notice.txt
> @@ -41,9 +41,9 @@ There you will find:
> +host-sources/+ subdirectories for target and host packages respectively.
> The source code for packages that set +<PKG>_REDISTRIBUTE = NO+ will not be
> saved.
> - Patches applied to some packages by Buildroot are distributed with the
> - Buildroot sources and are not duplicated in the +sources/+ and +host-sources/+
> - subdirectories.
> + Patches that were applied are also saved, along 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.
> * A manifest file (one for host and one for target packages) listing the
> configured packages, their version, license and related information.
> Some of this information might not be defined in Buildroot; such items are
> --
> 2.5.5
>
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Buildroot] [PATCH v2 3/3] docs: libtool patches are not handled by legal-info infrastructure.
2016-08-17 16:01 ` [Buildroot] [PATCH v2 3/3] docs: libtool patches are not handled by legal-info infrastructure Romain Naour
@ 2016-08-17 17:22 ` Yann E. MORIN
2016-08-19 21:34 ` Thomas Petazzoni
1 sibling, 0 replies; 9+ messages in thread
From: Yann E. MORIN @ 2016-08-17 17:22 UTC (permalink / raw)
To: buildroot
Romain, All,
On 2016-08-17 18:01 +0200, Romain Naour spake thusly:
> 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/legal-notice.txt | 4 ++++
> support/legal-info/README.header | 4 ++++
> 2 files changed, 8 insertions(+)
>
> diff --git a/docs/manual/legal-notice.txt b/docs/manual/legal-notice.txt
> index a4911f7..fd1e5aa 100644
> --- a/docs/manual/legal-notice.txt
> +++ b/docs/manual/legal-notice.txt
> @@ -44,6 +44,10 @@ There you will find:
> Patches that were applied are also saved, along 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.
> + Note: Buildroot applies additional patches to Libtool scripts of
> + autotools-based packages. These patches can be found under +support/libtool+
> + in the buildroot source and are not saved with the package sources due to
> + technical limitations. You may need to collect them manually.
I would have said:
[...] and, due to technical limitations, are not saved with the
other patches.
(Ditto below, of course).
Otherwise:
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Regards,
Yann E. MORIN.
> * A manifest file (one for host and one for target packages) listing the
> configured packages, their version, license and related information.
> Some of this information might not be defined in Buildroot; such items are
> diff --git a/support/legal-info/README.header b/support/legal-info/README.header
> index 1f3524f..ee34886 100644
> --- a/support/legal-info/README.header
> +++ b/support/legal-info/README.header
> @@ -20,6 +20,10 @@ 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: Buildroot applies additional patches to Libtool scripts of
> + autotools-based packages. These patches can be found under support/libtool
> + in the buildroot source and are not saved with the package sources due to
> + technical limitations. You may need to collect them 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
>
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Buildroot] [PATCH v2 1/3] core/pkg-autotools: don't use APPLY_PATCHES for libtool patches
2016-08-17 16:01 [Buildroot] [PATCH v2 1/3] core/pkg-autotools: don't use APPLY_PATCHES for libtool patches Romain Naour
2016-08-17 16:01 ` [Buildroot] [PATCH v2 2/3] docs: update legal-notice.txt Romain Naour
2016-08-17 16:01 ` [Buildroot] [PATCH v2 3/3] docs: libtool patches are not handled by legal-info infrastructure Romain Naour
@ 2016-08-18 21:59 ` Thomas Petazzoni
2 siblings, 0 replies; 9+ messages in thread
From: Thomas Petazzoni @ 2016-08-18 21:59 UTC (permalink / raw)
To: buildroot
Hello,
On Wed, 17 Aug 2016 18:01:08 +0200, Romain Naour wrote:
> Since [1] <package>-reconfigure target is broken.
>
> $ make elementary-reconfigure
> Applying buildroot-libtool-v2.4.4.patch using patch:
> Error: duplicate filename 'buildroot-libtool-v2.4.4.patch'
> Conflicting files are:
> already applied: buildroot/support/libtool/buildroot-libtool-v2.4.4.patch
> to be applied : buildroot/support/libtool/buildroot-libtool-v2.4.4.patch
>
> When a package uses AUTORECONF, the libtool patch can be applied a
> second time on the same ltmain.sh in the same directory as the
> <package>-reconfigure target is called. This is not a problem since
> autoreconf will overwrite the previously patched files. But with the
> check introduced by [1], apply-patches.sh throw an error when the
> package is reconfigured since the libtool patch is already present in
> .applied_patches_list.
>
> In addition to this, the .applied_patches_list file generated by
> apply-patches.sh while patching ltmain.sh is not in the top-level
> package source directory. Instead a duplicated .applied_patches_list
> is generated beside the patched ltmain.sh which can be in a
> subdirectory.
>
> As noticed by Arnout Vandecappelle [2], the apply-patches.sh script
> doesn't bring anything for the libtool patches.
>
> "apply_patches.sh does the following:
>
> * It handles directories -> not needed here.
> * It handles compressed patches and tarballs -> not needed.
> * It handles series files -> not needed.
> * It handles errors in case of multiple patches -> not needed since
> it's only one patch.
> * It detects errors based on *.rej files -> not needed since it's only
> a single patch so patch exit code is OK.
> * It writes the patch list -> for libtool, this is quite silly because
> it will be written in the directory where ltmain.sh is found, not in the
> top-level directory, so you have these patch lists spread over the
> source tree."
>
> So use patch directly rather than apply-patches.
>
> [1] 19241598147e7555dce40b6dd44b28ef22b67ed9
> [2] http://lists.busybox.net/pipermail/buildroot/2016-August/169810.html
>
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> Tested-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Cc: Arnout Vandecappelle <arnout@mind.be>
> ---
> v2: improve the commit log (Arnout)
> ---
> package/pkg-autotools.mk | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Buildroot] [PATCH v2 2/3] docs: update legal-notice.txt
2016-08-17 16:01 ` [Buildroot] [PATCH v2 2/3] docs: update legal-notice.txt Romain Naour
2016-08-17 17:19 ` Yann E. MORIN
@ 2016-08-19 14:20 ` Thomas Petazzoni
1 sibling, 0 replies; 9+ messages in thread
From: Thomas Petazzoni @ 2016-08-19 14:20 UTC (permalink / raw)
To: buildroot
Hello,
On Wed, 17 Aug 2016 18:01:09 +0200, Romain Naour wrote:
> Since 1273636fc686cd788b6de87be75dd0726cf8676c applied patches are also
> saved.
>
> 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/legal-notice.txt | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Buildroot] [PATCH v2 3/3] docs: libtool patches are not handled by legal-info infrastructure.
2016-08-17 16:01 ` [Buildroot] [PATCH v2 3/3] docs: libtool patches are not handled by legal-info infrastructure Romain Naour
2016-08-17 17:22 ` Yann E. MORIN
@ 2016-08-19 21:34 ` Thomas Petazzoni
2016-08-19 21:39 ` Yann E. MORIN
1 sibling, 1 reply; 9+ messages in thread
From: Thomas Petazzoni @ 2016-08-19 21:34 UTC (permalink / raw)
To: buildroot
Hello,
On Wed, 17 Aug 2016 18:01:10 +0200, Romain Naour wrote:
> 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/legal-notice.txt | 4 ++++
> support/legal-info/README.header | 4 ++++
> 2 files changed, 8 insertions(+)
Applied to master, after taking into account the suggestion from Yann
(hopefully correctly).
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Buildroot] [PATCH v2 3/3] docs: libtool patches are not handled by legal-info infrastructure.
2016-08-19 21:34 ` Thomas Petazzoni
@ 2016-08-19 21:39 ` Yann E. MORIN
0 siblings, 0 replies; 9+ messages in thread
From: Yann E. MORIN @ 2016-08-19 21:39 UTC (permalink / raw)
To: buildroot
Thomas, Romain, All,
On 2016-08-19 23:34 +0200, Thomas Petazzoni spake thusly:
> On Wed, 17 Aug 2016 18:01:10 +0200, Romain Naour wrote:
> > 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/legal-notice.txt | 4 ++++
> > support/legal-info/README.header | 4 ++++
> > 2 files changed, 8 insertions(+)
>
> Applied to master, after taking into account the suggestion from Yann
> (hopefully correctly).
Yep, good. Thanks! :-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2016-08-19 21:39 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-08-17 16:01 [Buildroot] [PATCH v2 1/3] core/pkg-autotools: don't use APPLY_PATCHES for libtool patches Romain Naour
2016-08-17 16:01 ` [Buildroot] [PATCH v2 2/3] docs: update legal-notice.txt Romain Naour
2016-08-17 17:19 ` Yann E. MORIN
2016-08-19 14:20 ` Thomas Petazzoni
2016-08-17 16:01 ` [Buildroot] [PATCH v2 3/3] docs: libtool patches are not handled by legal-info infrastructure Romain Naour
2016-08-17 17:22 ` Yann E. MORIN
2016-08-19 21:34 ` Thomas Petazzoni
2016-08-19 21:39 ` Yann E. MORIN
2016-08-18 21:59 ` [Buildroot] [PATCH v2 1/3] core/pkg-autotools: don't use APPLY_PATCHES for libtool patches Thomas Petazzoni
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.