From: Tor Arntsen <tor@spacetec.no>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: "Jonathan Nieder" <jrnieder@gmail.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Jakub Narebski" <jnareb@gmail.com>,
git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>
Subject: Re: [RFC PATCH] Makefile: Turn off the configure target by default
Date: Tue, 12 Oct 2010 11:10:18 +0200 [thread overview]
Message-ID: <AANLkTikG1U7CztwcbyDcsqsmeO9QXC2sA3e60mT_pL-7@mail.gmail.com> (raw)
In-Reply-To: <4CB41D50.9020208@drmicha.warpmail.net>
On Tue, Oct 12, 2010 at 10:33, Michael J Gruber
<git@drmicha.warpmail.net> wrote:
[configure etc]
> That thread was just the hair-trigger, so to say, there were many others
> in the past. But it's very typical. We often have "Don't use configure -
> it's second class"-type answers to build problems. I don't really
> remember that many "I use configure, and it works here"-type answers.
>
> Given the vigorous defense showing up here against deprecating configure
> (in the sense of declaring it second class), we can all be confident
> that there will be many knowledgeable and helpful answers to build
> problems for configure users, right?
At the moment './configure; make' works better than just 'make' on
Tru64 and AIX platforms. I have patches somewhere to improve just
'make' on those platforms but I haven't gotten around to post them yet
(need some polishing, or at least re-check against current .git). One
reason I figured it's no hurry is that ./configure actually takes care
of things there for now.
(The series posted by Gary from The Written Word, and mostly included
by now I think, was mainly based on TWW using configure on all
platforms btw. IIRC.)
-Tor
prev parent reply other threads:[~2010-10-12 9:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 7:47 [RFC PATCH] Makefile: Turn off the configure target by default Michael J Gruber
2010-10-11 7:59 ` Ævar Arnfjörð Bjarmason
2010-10-11 8:39 ` Jakub Narebski
2010-10-11 9:40 ` Ævar Arnfjörð Bjarmason
2010-10-11 12:10 ` Michael J Gruber
2010-10-11 12:37 ` [RFC PATCH] Makefile: point out "make" if "make configure" fails Ævar Arnfjörð Bjarmason
2010-10-11 15:06 ` Jakub Narebski
2010-10-11 20:46 ` Sverre Rabbelier
2010-10-11 15:18 ` [RFC PATCH] Makefile: Turn off the configure target by default Jakub Narebski
2010-10-11 15:28 ` Michael J Gruber
2010-10-11 16:21 ` Ævar Arnfjörð Bjarmason
2010-10-11 16:26 ` Jonathan Nieder
2010-10-12 8:33 ` Michael J Gruber
2010-10-12 9:10 ` Tor Arntsen [this message]
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTikG1U7CztwcbyDcsqsmeO9QXC2sA3e60mT_pL-7@mail.gmail.com \
--to=tor@spacetec.no \
--cc=avarab@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=jrnieder@gmail.com \
/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://80x24.org/mirrors/git.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).