From: Pablo Neira Ayuso <pablo@netfilter.org>
To: "Dmitry V. Levin" <ldv@altlinux.org>
Cc: Jan Engelhardt <jengelh@inai.de>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 1/6] build: also use libtool for install stage
Date: Wed, 20 Mar 2013 00:42:13 +0100 [thread overview]
Message-ID: <20130319234213.GA4246@localhost> (raw)
In-Reply-To: <20130306110836.GA4017@altlinux.org>
On Wed, Mar 06, 2013 at 03:08:36PM +0400, Dmitry V. Levin wrote:
[...]
> With regards to libtool's warnings about relinking, it happens to all
> hundreds of packages that manipulate RPATH entries during build, so
> the amount of annoyance among libtool users would hardly increase.
The thing is that the libtool patch for iptables was introduced to
resolve a linking problem in ip6t_NETMAP. That could have been easily
fixed with a little patch by using xtables_ip6mask_to_cidr.
I'm going to post a patch to fix that linking issue that way and roll
back to the previous situation where we were not using libtool.
next prev parent reply other threads:[~2013-03-19 23:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 13:59 Accumulated fixes v2 Jan Engelhardt
2013-01-28 13:59 ` [PATCH 1/6] build: also use libtool for install stage Jan Engelhardt
2013-02-05 3:30 ` Pablo Neira Ayuso
2013-03-05 23:16 ` Jan Engelhardt
2013-03-06 11:08 ` Dmitry V. Levin
2013-03-07 20:39 ` Jan Engelhardt
2013-03-19 23:42 ` Pablo Neira Ayuso [this message]
2013-01-28 13:59 ` [PATCH 2/6] build: do not dereference symlinks on installation Jan Engelhardt
2013-01-28 13:59 ` [PATCH 3/6] libxtables: centralize checking for a .save function Jan Engelhardt
2013-01-28 13:59 ` [PATCH 4/6] extensions: eui64: set userspacesize=0 Jan Engelhardt
2013-01-28 13:59 ` [PATCH 5/6] iptables: fall back to using save function when print is not defined Jan Engelhardt
2013-01-28 13:59 ` [PATCH 6/6] iptables: reword warning on using an alias Jan Engelhardt
2013-01-31 2:13 ` Accumulated fixes v2 Jan Engelhardt
2013-01-31 9:41 ` Pablo Neira Ayuso
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=20130319234213.GA4246@localhost \
--to=pablo@netfilter.org \
--cc=jengelh@inai.de \
--cc=ldv@altlinux.org \
--cc=netfilter-devel@vger.kernel.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.