From: Tomi Ollila <tomi.ollila@iki.fi>
To: David Bremner <david@tethera.net>,
Ronny Chevalier <chevalier.ronny@gmail.com>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH] configure: Add sanity checking for environment variables
Date: Wed, 20 May 2015 00:11:06 +0300 [thread overview]
Message-ID: <m2617onuhh.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <1432068728-26587-1-git-send-email-david@tethera.net>
On Tue, May 19 2015, David Bremner <david@tethera.net> wrote:
> Passing in environment variables incompatible with the compiler may
> cause other parts of the configure script to fail in hard to
> understand ways, so we abort early.
> ---
>
> This doesn't actually fix the problem Ronny points out, but a more
> serious one where configure can actually fail when using gcc, if
> e.g. nonsense is passed in CFLAGS.
>
> configure | 30 ++++++++++++++++++++++++++++--
> 1 file changed, 28 insertions(+), 2 deletions(-)
>
> diff --git a/configure b/configure
> index 4af7ba9..cf618e8 100755
> --- a/configure
> +++ b/configure
> @@ -269,6 +269,34 @@ dependencies are available:
> EOF
>
> errors=0
> +printf "int main(void){return 0;}\n" > minimal.c
> +
> +printf "Sanity checking C compilation environment... "
> +if ${CC} ${CFLAGS} ${CPPFLAGS} minimal.c ${LDFLAGS} -o minimal > /dev/null 2>&1
Looks good, but there is 2 spcs ^^ there (and same in CXX part)...
... also minimal.c is not removed if we exit early.
In the future we could think of writing all temp files to a subdirectory
which is cleared out using trap -- then we could drop all temp file
deletions... but now simple rm -f minimal minimal.c suffices
Tomi
> +then
> + printf "Ok.\n"
> +else
> + printf "Fail.\n"
> + errors=$((errors + 1))
> +fi
> +
> +printf "Sanity checking C++ compilation environment... "
> +if ${CXX} ${CXXFLAGS} ${CPPFLAGS} minimal.c ${LDFLAGS} -o minimal > /dev/null 2>&1
> +then
> + printf "Ok.\n"
> +else
> + printf "Fail.\n"
> + errors=$((errors + 1))
> +fi
> +
> +if [ $errors -gt 0 ]; then
> + cat <<EOF
> +*** Error: Initial sanity checking of environment failed. Please try
> +running configure in a clean environment, and if the problem persists,
> +report a bug.
> +EOF
> + exit 1
> +fi
>
> if pkg-config --version > /dev/null 2>&1; then
> have_pkg_config=1
> @@ -690,8 +718,6 @@ else
> fi
> rm -f compat/check_asctime
>
> -printf "int main(void){return 0;}\n" > minimal.c
> -
> printf "Checking for rpath support... "
> if ${CC} -Wl,--enable-new-dtags -Wl,-rpath,/tmp/ -o minimal minimal.c >/dev/null 2>&1
> then
> --
> 2.1.4
>
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch
next prev parent reply other threads:[~2015-05-19 21:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 18:31 configure tool Ronny Chevalier
2015-05-19 19:01 ` David Bremner
2015-05-19 19:08 ` Ronny Chevalier
2015-05-19 20:52 ` [PATCH] configure: Add sanity checking for environment variables David Bremner
2015-05-19 21:11 ` Tomi Ollila [this message]
2015-05-20 8:12 ` David Bremner
2015-05-20 8:37 ` Tomi Ollila
2015-05-20 8:41 ` Tomi Ollila
2015-05-20 8:48 ` Tomi Ollila
2015-05-20 9:45 ` David Bremner
2015-05-20 10:45 ` Tomi Ollila
2015-05-23 18:33 ` 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=m2617onuhh.fsf@guru.guru-group.fi \
--to=tomi.ollila@iki.fi \
--cc=chevalier.ronny@gmail.com \
--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).