From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 1/8] build: also use libtool for install stage
Date: Mon, 28 Jan 2013 12:33:51 +0100 [thread overview]
Message-ID: <20130128113351.GA15781@1984> (raw)
In-Reply-To: <1359056278-27618-2-git-send-email-jengelh@inai.de>
On Thu, Jan 24, 2013 at 08:37:51PM +0100, Jan Engelhardt wrote:
> The just-built library has DT_RPATH entries to be runnable from
> whereever it is. If we just install that, the distro build systems
> will throw warnings like
>
> (Open Build Service) ERROR: RPATH
> "/home/abuild/rpmbuild/BUILD/iptables-1.4.17a/libxtables/.libs"
> on /home/abuild/rpmbuild/BUILDROOT/iptables-1.4.17a-0.x86_64/usr/lib64/xtables/libxt_unclean.so
> is not allowed
>
> These RPATH entries are indeed undesired for libraries is in a system
> location, which is why libtool produces another copy of the library on
> installation. The makefile however missed using libtool during
> installation (introduced with commit v1.4.17-1-g68e77a2).
> This patch now resolves this.
I hit this with this patch:
make[1]: ...
libtool: install: warning: relinking `libxt_AUDIT.la'
libtool: install: warning: relinking `libxt_CHECKSUM.la'
libtool: install: warning: relinking `libxt_CLASSIFY.la'
libtool: install: warning: relinking `libxt_CONNMARK.la'
libtool: install: warning: relinking `libxt_CONNSECMARK.la'
libtool: install: warning: relinking `libxt_CT.la'
libtool: install: warning: relinking `libxt_DSCP.la'
libtool: install: warning: relinking `libxt_HMARK.la'
libtool: install: warning: relinking `libxt_IDLETIMER.la'
libtool: install: warning: relinking `libxt_LED.la'
...
next prev parent reply other threads:[~2013-01-28 11:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 19:37 Accumulated fixes Jan Engelhardt
2013-01-24 19:37 ` [PATCH 1/8] build: also use libtool for install stage Jan Engelhardt
2013-01-28 11:33 ` Pablo Neira Ayuso [this message]
2013-01-28 13:23 ` Jan Engelhardt
2013-01-24 19:37 ` [PATCH 2/8] build: do not dereference symlinks on installation Jan Engelhardt
2013-01-24 19:37 ` [PATCH 3/8] libxtables: centralize checking for a .save function Jan Engelhardt
2013-01-28 11:35 ` Pablo Neira Ayuso
2013-01-28 13:39 ` Jan Engelhardt
2013-01-24 19:37 ` [PATCH 4/8] extensions: eui64: set userspacesize=0 Jan Engelhardt
2013-01-24 19:37 ` [PATCH 5/8] extensions: S/DNPT: add missing save function Jan Engelhardt
2013-01-28 11:36 ` Pablo Neira Ayuso
2013-01-24 19:37 ` [PATCH 6/8] iptables: fall back to using save function when print is not defined Jan Engelhardt
2013-01-28 11:37 ` Pablo Neira Ayuso
2013-01-24 19:37 ` [PATCH 7/8] iptables: reword warning on using an alias Jan Engelhardt
2013-01-24 19:37 ` [PATCH 8/8] build: fix libiptc build failure on old linux-glibc-devel headers Jan Engelhardt
2013-01-28 11: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=20130128113351.GA15781@1984 \
--to=pablo@netfilter.org \
--cc=jengelh@inai.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).