-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05-10-10 17:15, Tom Rini wrote: > Koen Kooi wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 05-10-10 09:43, Khem Raj wrote: >>> Hi >>> >>> Following set of patches is intial support for getting libtool 2.4 into >>> openemebedded. I have so far built minimal-image for two machines >>> successfully >>> >>> The big change that libtool 2.4 brings is sysroot support and I have >>> added >>> support to use this feature. It should make our life easier. >> >> I'm a bit concerned about the way this is implemented, it seems to for >> libtool 2.4 onto everyone since it changes e.g. autotools.bbclass. Is >> that intended? If so we need signoffs from each and every distro >> maintainer *and* from the maemo-compat folks as well. >> Unless there is a way to make the new features conditional on the >> libtool version. > > It shouldn't be too bad, implementation wise, to set LIBTOOL_HAS_SYSROOT > or similar and test for that.
That was I was thinking, make it opt in for now and have the trailblazers (angstrom, shr) find & fix issues before RFC it to make it the default. > But can we also set a phase out date for > older libtool, even if maemo-compat isn't possible (given chinhook pins > to 1.5, I bet it's not) ? A phase-out would be good, I'm not sure how many people are going to use maemo-compat (and friends) from .dev in a few months from now. Doing something like this is a lot bigger than a toolchain change, so I don't think 2 signoffs is enough. My proposal: 1) add libtool recipes to .dev 2) create branch for sysroot changes (with or without LIBTOOL_HAS_SYSROOT) 3) gather test reports for said branch 4) fix issues 5) create branch with LIBTOOL_HAS_SYSROOT and propose for merging. Does that sounds like a decent plan to go forward? regards, Koen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFMq06OMkyGM64RGpERAkfXAJ0YMrdthZ0hG6JzeV56QkV8ZO/oKACdHXlF dH1LJFmKhCVg1dB8xMDJOIU= =uLnX -----END PGP SIGNATURE----- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
