From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 0/6] libtool 2.4 upgrade
Date: Tue, 05 Oct 2010 18:13:02 +0200 [thread overview]
Message-ID: <i8fiqe$f3b$1@dough.gmane.org> (raw)
In-Reply-To: <4CAB4112.3070505@mentor.com>
-----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-----
next prev parent reply other threads:[~2010-10-05 16:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 7:43 [PATCH 0/6] libtool 2.4 upgrade Khem Raj
2010-10-05 7:43 ` [PATCH 1/6] libtool-2.4: Add recipes for libtool 2.4 Khem Raj
2010-10-05 8:16 ` Holger Freyther
2010-10-05 18:35 ` Khem Raj
2010-10-05 7:43 ` [PATCH 2/6] bitbake.conf: No need to add sysroot to -rpath-link or -L in TARGET_LDFLAGS Khem Raj
2010-10-05 7:44 ` [PATCH 3/6] autotools.bbclass: Add --with-sysroot to configure Khem Raj
2010-10-05 7:44 ` [PATCH 4/6] cross.bbclass, staging.bbclass, utils.bbclass: With sysroot support in libtool, its not needed to edit .la files Khem Raj
2010-10-05 7:44 ` [PATCH 5/6] insane.bbclass: Do not check for installed=yes in " Khem Raj
2010-10-05 7:44 ` [PATCH 6/6] gnutls_2.10.1.bb: Update to libtools 2.4 macros Khem Raj
2010-10-05 8:24 ` Holger Freyther
2010-10-05 18:37 ` Khem Raj
2010-10-05 10:38 ` [PATCH 0/6] libtool 2.4 upgrade Koen Kooi
2010-10-05 13:15 ` Frans Meulenbroeks
2010-10-05 15:15 ` Tom Rini
2010-10-05 16:13 ` Koen Kooi [this message]
2010-10-05 17:50 ` Frans Meulenbroeks
2010-10-05 18:41 ` Khem Raj
2010-10-05 18:40 ` Khem Raj
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='i8fiqe$f3b$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
/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