libtool version update 2.4.2
PATCH 1/1 libtool version update 2.4.2
--- package/libtool/libtool.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
package/libtool/libtool.mk +1 -1
@@ -3,7 +3,7 @@ # libtool # ############################################################# -LIBTOOL_VERSION = 2.2.10 +LIBTOOL_VERSION = 2.4.2 LIBTOOL_SOURCE = libtool-$(LIBTOOL_VERSION).tar.gz LIBTOOL_SITE = $(BR2_GNU_MIRROR)/libtool LIBTOOL_INSTALL_STAGING = YES
Signature · 1 line
1.7.11.3
PATCH 1/1 libtool version update 2.4.2
Alexander,
package/libtool/libtool.mk line 6
Quoted 2 lines · Alexander Khryukin
package/libtool/libtool.mk +1
-1-LIBTOOL_VERSION = 2.2.10 +LIBTOOL_VERSION = 2.4.2
How much testing did you give to this version bump? A libtool version bump is a very sensitive operation, as host-libtool is used to autoreconfigure many packages in Buildroot. Therefore, this patch needs a good amount of testing before being committed (ideally testing that all packages having <foo>_AUTORECONF = YES still build).
Thanks,
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com
PATCH 1/1 libtool version update 2.4.2
2012/11/10 Thomas Petazzoni <[email protected]>
Quoted 13 lines
Alexander,
package/libtool/libtool.mk line 6
Quoted 2 lines · Alexander Khryukin
package/libtool/libtool.mk +1
-1-LIBTOOL_VERSION = 2.2.10 +LIBTOOL_VERSION = 2.4.2How much testing did you give to this version bump? A libtool version bump is a very sensitive operation, as host-libtool is used to autoreconfigure many packages in Buildroot. Therefore, this patch needs a good amount of testing before being committed (ideally testing that all packages having <foo>_AUTORECONF = YES still build).
Quoted 9 lines
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
With new libtool i built my system many times
and it works.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121110/1f5fde48/attachment-0001.html>
PATCH 1/1 libtool version update 2.4.2
In reply to Thomas PetazzoniQuoted 4 lines · Thomas Petazzoni
Alexander,
On Fri, 9 Nov 2012 16:38:52 +0400, Alexander Khryukin wrote:
Quoted 8 lines
package/libtool/libtool.mk line 6
Quoted 2 lines
package/libtool/libtool.mk +1
-1-LIBTOOL_VERSION = 2.2.10 +LIBTOOL_VERSION = 2.4.2How much testing did you give to this version bump? A libtool version bump is a very sensitive operation, as host-libtool is used to autoreconfigure many packages in Buildroot. Therefore, this patch needs a good amount of testing before being committed (ideally testing that all packages having<foo>_AUTORECONF = YES still build).
Can't we rely on the autobuilders to do that?
That said, I wouldn't do this for 2012.11 anymore...
Regards,
Arnout
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286540 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: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
PATCH 1/1 libtool version update 2.4.2
Quoted 15 lines · Arnout Vandecappelle
Quoted 4 lines · Thomas Petazzoni
Alexander,
On Fri, 9 Nov 2012 16:38:52 +0400, Alexander Khryukin wrote:
Quoted 9 lines
package/libtool/libtool.mk line 6
Quoted 2 lines
package/libtool/libtool.mk +1
-1-LIBTOOL_VERSION = 2.2.10 +LIBTOOL_VERSION = 2.4.2How much testing did you give to this version bump? A libtool version bump is a very sensitive operation, as host-libtool is used to autoreconfigure many packages in Buildroot. Therefore, this patch needs a good amount of testing before being committed (ideally testing that all packages having<foo>_AUTORECONF = YES still build).
Quoted 1 line
Can't we rely on the autobuilders to do that?
Sure, we'll certainly rely on the autobuilders for a complete testing. But I wanted to know if it had been tested again 2 packages or 20-40 packages, which makes quite a bit of difference :)
Quoted 1 line
That said, I wouldn't do this for 2012.11 anymore...
For sure, it should not be part of 2012.11, we already have enough issues to fix.
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com
PATCH 1/1 libtool version update 2.4.2
Am 11.11.2012 23:05, schrieb Thomas Petazzoni:
Quoted 14 lines · Arnout Vandecappelle
Quoted 13 lines · Thomas Petazzoni
Quoted 12 lines
Alexander,
package/libtool/libtool.mk line 6
Quoted 2 lines · Alexander Khryukin
package/libtool/libtool.mk +1
-1-LIBTOOL_VERSION = 2.2.10 +LIBTOOL_VERSION = 2.4.2How much testing did you give to this version bump? A libtool version bump is a very sensitive operation, as host-libtool is used to autoreconfigure many packages in Buildroot. Therefore, this patch needs a good amount of testing before being committed (ideally testing that all packages having<foo>_AUTORECONF = YES still build).
Quoted 2 lines
Quoted 1 line
Can't we rely on the autobuilders to do that?
Sure, we'll certainly rely on the autobuilders for a complete testing.
Hello,
did you ever think about inventing a kind of "testing" branch with a seperate autobuilder running on? That could keep major build problems away from the master branch.
Just my 2 cents
Stephan
Quoted 8 lines
But I wanted to know if it had been tested again 2 packages or 20-40 packages, which makes quite a bit of difference :)
Quoted 1 line
That said, I wouldn't do this for 2012.11 anymore...
For sure, it should not be part of 2012.11, we already have enough issues to fix.
Thomas
Signature · 4 lines
reLinux - Stephan Hoffmann Am Schmidtgrund 124 50765 K?ln Tel. +49.221.95595-19 Fax: -64 www.reLinux.de sho at reLinux.de
PATCH 1/1 libtool version update 2.4.2
2012/11/12 Stephan Hoffmann <[email protected]>
Quoted 43 lines
Am 11.11.2012 23:05, schrieb Thomas Petazzoni:
Quoted 14 lines · Arnout Vandecappelle
Quoted 13 lines · Thomas Petazzoni
Quoted 12 lines
Alexander,
package/libtool/libtool.mk line 6
Quoted 2 lines · Alexander Khryukin
package/libtool/libtool.mk +1
-1-LIBTOOL_VERSION = 2.2.10 +LIBTOOL_VERSION = 2.4.2How much testing did you give to this version bump? A libtool version bump is a very sensitive operation, as host-libtool is used to autoreconfigure many packages in Buildroot. Therefore, this patch needs a good amount of testing before being committed (ideally testing that all packages having<foo>_AUTORECONF = YES still build).
Quoted 2 lines
Quoted 1 line
Can't we rely on the autobuilders to do that?
Sure, we'll certainly rely on the autobuilders for a complete testing.
Hello,
did you ever think about inventing a kind of "testing" branch with a seperate autobuilder running on? That could keep major build problems away from the master branch.
Just my 2 cents
Stephan
Quoted 8 lines
But I wanted to know if it had been tested again 2 packages or 20-40 packages, which makes quite a bit of difference :)
Quoted 1 line
That said, I wouldn't do this for 2012.11 anymore...
For sure, it should not be part of 2012.11, we already have enough issues to fix.
Thomas
--
reLinux - Stephan Hoffmann
Am Schmidtgrund 124 50765 K?ln
Tel. +49.221.95595-19 Fax: -64
www.reLinux.de sho at reLinux.de
Quoted 5 lines
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
I tested new libtool for all packages in Develop section + a lot of others.
Also i can share own .config
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121112/a5d7ce44/attachment.html>
PATCH 1/1 libtool version update 2.4.2
In reply to Stephan HoffmannStephan,
Quoted 3 lines · Stephan Hoffmann
did you ever think about inventing a kind of "testing" branch with a seperate autobuilder running on? That could keep major build problems away from the master branch.
Yes, this has been discussed during the Developers Meeting, at least for the "next" branch that gets created once -rc1 is out, to accumulate patches for the next release.
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com
PATCH 1/1 libtool version update 2.4.2
Quoted 11 lines · Thomas Petazzoni
Stephan,
Quoted 3 lines · Stephan Hoffmann
did you ever think about inventing a kind of "testing" branch with a seperate autobuilder running on? That could keep major build problems away from the master branch.
Yes, this has been discussed during the Developers Meeting, at least for the "next" branch that gets created once -rc1 is out, to accumulate patches for the next release.
Actually it does make sense to have it in general. We could allow more committers
on that branch, and Peter could cherry-pick from it, which could save him a few seconds per patch. And it could make master slightly more stable, because only patches that don't kill the autobuilders would get cherry-picked.
Maybe something to discuss in February.
Regards,
Arnout
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286540 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: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F