From: Tomi Ollila <tomi.ollila@iki.fi>
To: david@tethera.net, notmuch@notmuchmail.org
Cc: David Bremner <bremner@debian.org>
Subject: Re: [PATCH] configure: really expand libdir_expanded
Date: Wed, 28 Nov 2012 14:31:21 +0200 [thread overview]
Message-ID: <m2ip8pewo6.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <1354105552-31297-1-git-send-email-david@tethera.net>
On Wed, Nov 28 2012, david@tethera.net wrote:
> From: David Bremner <bremner@debian.org>
>
> It turns out that if people really use configure in autotools style and pass
> libdir containing '${prefix}/foo' then the ldconfig previously failed.
>
> This uses sed for portability (versus bash parameter expansion with
> substitution) and hopefully a bit more robustness than blindly
> parameter expanding the string.
> ---
For the record: +1
Tomi
> configure | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/configure b/configure
> index ea8a1ad..460fcfc 100755
> --- a/configure
> +++ b/configure
> @@ -236,7 +236,12 @@ done
> # Makefile.config file later like most values), because we need to
> # actually investigate this value compared to the ldconfig_paths value
> # below.
> -libdir_expanded=${LIBDIR:-${PREFIX}/lib}
> +if [ -z "$LIBDIR" ] ; then
> + libdir_expanded="${PREFIX}/lib"
> +else
> + # very non-general variable expansion
> + libdir_expanded=`echo "$LIBDIR" | sed "s|\\${prefix}|${PREFIX}|g; s|\\$prefix/|${PREFIX}/|; s|//*|/|g"`
> +fi
>
> cat <<EOF
> Welcome to Notmuch, a system for indexing, searching and tagging your email.
> --
> 1.7.10.4
>
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch
next prev parent reply other threads:[~2012-11-28 12:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 12:25 [PATCH] configure: really expand libdir_expanded david
2012-11-28 12:31 ` Tomi Ollila [this message]
2012-12-01 12:32 ` David Bremner
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2ip8pewo6.fsf@guru.guru-group.fi \
--to=tomi.ollila@iki.fi \
--cc=bremner@debian.org \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).