From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Notmuch Mail <notmuch@notmuchmail.org>
Subject: bug in configure script
Date: Fri, 01 Jun 2012 11:17:05 -0700 [thread overview]
Message-ID: <87pq9ivqvy.fsf@servo.finestructure.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
There's a bug in the configure script that is causing auto-reruns of
./configure to not inherit original command line options if there was
more than one. For instance, if I run:
./configure --with-gmime-version=2.4 --prefix=/home/jrollins/opt/notmuch
Then in Makefile.config I get:
configure_options = --with-gmime-version=2.4--prefix=/home/jrollins/opt/notmuch
This means that auto-reruns of configure will not get the proper
options.
I tracked this down to an issue with IFS and /bin/sh. The first line of
./configure is:
readonly DEFAULT_IFS=$IFS
DEFAULT_IFS is then used to reset IFS after it is modified within the
script. The problem is that /bin/sh is setting DEFAULT_IFS to be NULL
(i.e. ''), which leads to no separation between variables when "$@" is
expanded (which is itself problematic since I don't think "@" should use
the IFS when expanded). So this might be a bug in dash. I don't know.
In any event we need to fix this somehow. I see two obvious solutions:
* use /bin/bash. This a one line diff that fixes the problem
immediately.
* replace:
IFS=$DEFAULT_IFS
with:
unset IFS
Unsetting IFS also resets IFS to the default, without going through
this intermediate step.
I'm ok with either solution, but I'll wait for some feedback since I
imagine someone will have an opinion.
jamie.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next reply other threads:[~2012-06-01 18:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 18:17 Jameson Graef Rollins [this message]
2012-06-02 11:02 ` bug in configure script Tomi Ollila
2012-06-02 18:23 ` Jameson Graef Rollins
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=87pq9ivqvy.fsf@servo.finestructure.net \
--to=jrollins@finestructure.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).