From: Mike Frysinger <vapier@gentoo.org>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] extensions: fix linking against -lip6tc
Date: Sun, 30 Dec 2012 19:51:46 -0500 [thread overview]
Message-ID: <201212301951.47241.vapier@gentoo.org> (raw)
In-Reply-To: <20121230233828.GA30455@1984>
[-- Attachment #1: Type: Text/Plain, Size: 856 bytes --]
On Sunday 30 December 2012 18:38:28 Pablo Neira Ayuso wrote:
> Hi Mike,
>
> On Sun, Dec 30, 2012 at 06:11:47PM -0500, Mike Frysinger wrote:
> > The current build forgets to specify a path to find libip6tc which means
> > it either fails (if there is no libip6tc in the system), or links against
> > an old version (if there is one in the system).
>
> We already got a similar patch fix for that issue:
>
> http://patchwork.ozlabs.org/patch/208133/
>
> Can you give it a try and check if it also fixes the problem for you?
adding an -L path to the non-.libs/ subdir doesn't make sense when the
existing code (the -lxtables stuff) only uses .libs/.
really the best thing would to stop grubbing around in libtool internals and
use libtool to link considering it was used to generate the other libraries in
the first place.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-12-31 0:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-30 23:11 [PATCH] extensions: fix linking against -lip6tc Mike Frysinger
2012-12-30 23:38 ` Pablo Neira Ayuso
2012-12-31 0:51 ` Mike Frysinger [this message]
2012-12-31 5:54 ` [PATCH] build: resolve link failure for ip6t_NETMAP Jan Engelhardt
2013-01-02 4:03 ` Mike Frysinger
2013-01-02 8:42 ` Jan Engelhardt
2013-01-02 8:47 ` Jan Engelhardt
2013-01-02 17:23 ` Mike Frysinger
2013-01-02 23:50 ` Pablo Neira Ayuso
2013-01-11 23:34 ` Dmitry V. Levin
2013-01-12 0:00 ` Dmitry V. Levin
2013-01-12 1:37 ` Jan Engelhardt
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=201212301951.47241.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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.