Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Tentative conclusion on the libtool work
Date: Thu, 7 Oct 2010 16:57:44 +0200	[thread overview]
Message-ID: <20101007165744.490fca33@surf> (raw)
In-Reply-To: <20100928223652.6dc72083@surf>

On Tue, 28 Sep 2010 22:36:52 +0200
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:

> In my opinion, we should settle on a solution before mid-october, in
> order to merge it before the end of october and give us enough time
> for testing before the release at the end of november. Considering
> how much time Martin and Lionel have dedicated to this issue, I think
> that their respective work deserve some attention.

From the various comments on this list and discussions on IRC, it seems
that the consensus is that :

 *) We should merge Martin Banky's work, as it keeps the existing
    known-working approach and just extends it to support packages that
    have used libtool 2.2 to generate their libtool script.

    Peter, if you're ok, I can give some build tests to Martin's work
    and send you a pull request for it.

 *) We should upgrade our own libtool package to libtool 2.2, so that
    packages such as libgtk2 that needs to be autoreconf'ed *and* need
    libtool >= 2.2 can actually be autoreconf'ed.

    Lionel, would you mind preparing such a patch set ?

Do we agree on this solution ?

Ideally, it'd be nice to merge it within the next few weeks, at least
before the end of October, so that we can bump libgtk2 and have all
this in 2010.11.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2010-10-07 14:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-28 20:36 [Buildroot] Libtool work: a tentative summary Thomas Petazzoni
2010-09-28 23:26 ` Lionel Landwerlin
2010-09-29  8:32 ` Paulius Zaleckas
2010-09-29  8:51   ` Thomas Petazzoni
2010-09-29 11:01     ` Paulius Zaleckas
2010-09-29 11:12       ` [Buildroot] On internal vs. external toolchains Thomas Petazzoni
2010-09-29 19:59       ` [Buildroot] Libtool work: a tentative summary Martin Banky
2010-10-03 13:22 ` Lionel Landwerlin
2010-10-03 14:22   ` Thomas Petazzoni
2010-10-03 22:36     ` Martin Banky
2010-10-03 23:47       ` Lionel Landwerlin
2010-10-04  1:19         ` Martin Banky
2010-10-04  8:09           ` Lionel Landwerlin
2010-10-05  0:04             ` Lionel Landwerlin
2010-10-07 14:57 ` Thomas Petazzoni [this message]
2010-10-07 16:34   ` [Buildroot] Tentative conclusion on the libtool work Lionel Landwerlin

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=20101007165744.490fca33@surf \
    --to=thomas.petazzoni@free-electrons.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