From: Holger Freyther <holger+oe@freyther.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 6/6] gnutls_2.10.1.bb: Update to libtools 2.4 macros.
Date: Tue, 05 Oct 2010 16:24:12 +0800 [thread overview]
Message-ID: <4CAAE0AC.4040701@freyther.de> (raw)
In-Reply-To: <1286264643-6352-7-git-send-email-raj.khem@gmail.com>
On 10/05/2010 03:44 PM, Khem Raj wrote:
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> recipes/gnutls/gnutls-2.10.1/libtool-update.patch |10965 +++++++++++++++++++++
> recipes/gnutls/gnutls_2.10.1.bb | 3 +-
> 2 files changed, 10967 insertions(+), 1 deletions(-)
> create mode 100644 recipes/gnutls/gnutls-2.10.1/libtool-update.patch
normally we tend to just remove the copy of libtool... autoreconf --install
will just install the new version back. Why is that not possible here?
next prev parent reply other threads:[~2010-10-05 8:24 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 [this message]
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
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=4CAAE0AC.4040701@freyther.de \
--to=holger+oe@freyther.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.