unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Ronny Chevalier <chevalier.ronny@gmail.com>, notmuch@notmuchmail.org
Subject: Re: configure tool
Date: Tue, 19 May 2015 21:01:15 +0200	[thread overview]
Message-ID: <87y4kkfl38.fsf@maritornes.cs.unb.ca> (raw)
In-Reply-To: <CABPZE7JWDGnsnS-TFRRTOdSbC09qiRS4gtL=rPP1aXeiQEMbug@mail.gmail.com>

Ronny Chevalier <chevalier.ronny@gmail.com> writes:

> Hi,
>
> I'm curious about the reason behind choosing to do your own configure
> tool instead of using tools like autotools or cmake?

I guess the most relevant discussion is not that recent:

    http://mid.gmane.org/1258897630-22282-1-git-send-email-jeff@ocjtech.us

and to a lesser extent the discussion starting atL

    http://article.gmane.org/gmane.mail.notmuch.general/635

> For example, I noticed that the part that check if the compiler
> options are supported, is not working. Try adding a flag supported by
> gcc but not by clang and use clang to compile or vice-versa.

Sure, of course there can be bugs, just as in any configuration system.
Can you give a more specific recipe to reproduce it?

Thanks,

d

  reply	other threads:[~2015-05-19 19:03 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 [this message]
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
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=87y4kkfl38.fsf@maritornes.cs.unb.ca \
    --to=david@tethera.net \
    --cc=chevalier.ronny@gmail.com \
    --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).