From: Karel Zak <kzak@redhat.com>
To: Ruediger Meier <sweet_f_a@gmx.de>
Cc: util-linux@vger.kernel.org
Subject: Re: build-sys: how to install pylibmount after libmount?
Date: Wed, 4 Jun 2014 12:21:17 +0200 [thread overview]
Message-ID: <20140604102117.GU9000@x2.net.home> (raw)
In-Reply-To: <201406031552.50670.sweet_f_a@gmx.de>
On Tue, Jun 03, 2014 at 03:52:50PM +0200, Ruediger Meier wrote:
> Hi,
>
> This should be easy to reproduce if you don't have a global installed
> libmount.
>
> $ sudo mkdir /usr/lib64/away
> $ sudo mv /usr/lib64/libmount.* /usr/lib64/away
>
> $ ./configure --disable-use-tty-group \
> --prefix=/tmp/dest \
Just note, it's usually bad idea to override the default prefix
(especially for package like util-linux), it's better to use
standard prefix and use "make install DESTDIR=/tmp/dest".
> Unfortunately some systems set per default
> link_all_deplibs=no
> instead of "unknown" in ./libtool. Don't know whether this is a bug in
> libtool or automake macros. But we could work around this if we would
> make sure to install pylibmount always after libmount.
>
> This is how it looks in Makefile.in:
> install-exec-am: install-binPROGRAMS install-dist_usrbin_execSCRIPTS \
> install-pylibmountexecLTLIBRARIES \
> install-pylibmountexecSCRIPTS install-sbinPROGRAMS \
> install-usrbin_execPROGRAMS install-usrlib_execLTLIBRARIES \
> install-usrsbin_execPROGRAMS
> @$(NORMAL_INSTALL)
> $(MAKE) $(AM_MAKEFLAGS) install-exec-hook
>
> How could we force to put
> install-pylibmountexecLTLIBRARIES
> after
> install-usrlib_execLTLIBRARIES
hmm.. I don't know, I think it's libtool job to generate the right order.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2014-06-04 10:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 13:52 build-sys: how to install pylibmount after libmount? Ruediger Meier
2014-06-04 10:21 ` Karel Zak [this message]
2014-06-04 10:45 ` Ruediger Meier
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=20140604102117.GU9000@x2.net.home \
--to=kzak@redhat.com \
--cc=sweet_f_a@gmx.de \
--cc=util-linux@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).