From: llandwerlin at gmail.com <llandwerlin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [review request] rework of libtool
Date: Sat, 18 Sep 2010 19:59:42 +0200 [thread overview]
Message-ID: <1284832789-22631-1-git-send-email-llandwerlin@gmail.com> (raw)
This patch serie tries to rework how buildroot deals with libtooled
packages.
The main thing to retain is that instead of dealing with the libtool
scripts shipped within the packages, we want to use our own slightly
modified libtool version. The downside of this approach is that now,
we have to turn on autoreconfiguration on libtooled packages. And so
we need to make a pass on all concerned packages to make sure nothing
is broken. Otherwise, most of the concerned packages just need a
simple modification of the <PKG_NAME>_AUTORECONF and
<PKG_NAME>_LIBTOOL_PATCH variables.
This series shows the modifications to bring for a few packages.
next reply other threads:[~2010-09-18 17:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-18 17:59 llandwerlin at gmail.com [this message]
2010-09-18 17:59 ` [Buildroot] [PATCH 1/7] libtool: bump to 2.2.6b + introduce 2 libtool packages + cross compile patch llandwerlin at gmail.com
2010-09-18 17:59 ` [Buildroot] [PATCH 2/7] package: modifications to work with new libtool policy llandwerlin at gmail.com
2010-09-18 17:59 ` [Buildroot] [PATCH 3/7] tslib: Fix installation with new autotools policy llandwerlin at gmail.com
2010-09-18 17:59 ` [Buildroot] [PATCH 4/7] bison: add host rules llandwerlin at gmail.com
2010-09-29 7:03 ` Thomas Petazzoni
2010-09-18 17:59 ` [Buildroot] [PATCH 5/7] expat: comply with new libtool policy llandwerlin at gmail.com
2010-09-18 17:59 ` [Buildroot] [PATCH 6/7] sysstat: bump to 9.1.5 and " llandwerlin at gmail.com
2010-09-18 17:59 ` [Buildroot] [PATCH 7/7] gstreamer: allow autoreconfigure with gettext 0.18 llandwerlin at gmail.com
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=1284832789-22631-1-git-send-email-llandwerlin@gmail.com \
--to=llandwerlin@gmail.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