From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH 1/2] add configure option --with-root-libdir
Date: Mon, 27 Aug 2018 11:51:14 -0400 [thread overview]
Message-ID: <20180827155114.GG2311@thunk.org> (raw)
In-Reply-To: <20180820030407.13225-1-tytso@mit.edu>
On Sun, Aug 19, 2018 at 11:04:06PM -0400, Theodore Ts'o wrote:
> This allows the development link libraries to be installed in
> /usr/lib, while the run-libraries are installed in /lib, which is
> required by Debian policy. This can be done via:
>
> configure --prefix=/ --libdir=/usr/lib --with-root-libdir=/lib
>
> The technique of working around libtool's inflexibility is borrowed
> from util-linux.
>
> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Ping? This is needed (and is applied) for the Debian packaging of
f2fs-tools. See patch #0001 at:
https://salsa.debian.org/debian/f2fs-tools/tree/master/debian/patches
- Ted
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
next prev parent reply other threads:[~2018-08-27 15:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 3:04 [PATCH 1/2] add configure option --with-root-libdir Theodore Ts'o
2018-08-20 3:04 ` [PATCH 2/2] Ask git to ignore the generated sg_write_buffer executable Theodore Ts'o
2018-08-20 7:21 ` Chao Yu
2018-08-27 15:51 ` Theodore Y. Ts'o [this message]
2018-08-27 16:57 ` [PATCH 1/2] add configure option --with-root-libdir Jaegeuk Kim
2018-08-27 23:56 ` Theodore Y. Ts'o
2018-08-28 7:12 ` Jaegeuk Kim
2018-08-28 14:25 ` Theodore Y. Ts'o
2018-08-28 16:59 ` Jaegeuk Kim
2018-08-29 3:10 ` [PATCH 1/2] add cotnfigure " Theodore Y. Ts'o
2018-08-29 21:04 ` Jaegeuk Kim
2018-08-29 23:51 ` Theodore Y. Ts'o
2018-08-28 3:43 ` [PATCH 1/2] add configure " Chao Yu
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=20180827155114.GG2311@thunk.org \
--to=tytso@mit.edu \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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.