From: Olivier Galibert <galibert@pobox.com>
To: git@vger.kernel.org
Subject: Re: Autoconf/Automake
Date: Thu, 15 Jun 2006 20:19:22 +0200 [thread overview]
Message-ID: <20060615181922.GA36286@dspnet.fr.eu.org> (raw)
In-Reply-To: <e6s7eb$78h$1@sea.gmane.org>
On Thu, Jun 15, 2006 at 08:03:56PM +0200, Jakub Narebski wrote:
> Does autoconf generate configure script in POSIX shell, or in bash?
It seems that it still generates bare /bin/sh compatible scripts.
ICBvery easilyW, though.
OG.
next prev parent reply other threads:[~2006-06-15 18:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 22:27 Autoconf/Automake Pavel Roskin
2006-06-14 22:45 ` Autoconf/Automake Linus Torvalds
2006-06-14 22:54 ` Autoconf/Automake Bertrand Jacquin
2006-06-14 23:18 ` Autoconf/Automake Timo Hirvonen
2006-06-15 7:24 ` Autoconf/Automake Yann Dirson
2006-06-15 13:31 ` Autoconf/Automake Alex Riesen
2006-06-15 16:32 ` Autoconf/Automake Yann Dirson
2006-06-15 17:02 ` Autoconf/Automake Linus Torvalds
2006-06-15 17:48 ` Autoconf/Automake Olivier Galibert
2006-06-15 18:03 ` Autoconf/Automake Jakub Narebski
2006-06-15 18:19 ` Olivier Galibert [this message]
2006-06-16 18:23 ` Autoconf/Automake Petr Baudis
2006-06-16 9:06 ` Autoconf/Automake Jerome Lovy
2006-06-15 20:17 ` Autoconf/Automake Yakov Lerner
2006-06-15 21:14 ` Autoconf/Automake Yann Dirson
2006-06-15 22:54 ` Autoconf/Automake Linus Torvalds
2006-06-15 23:10 ` Autoconf/Automake Johannes Schindelin
2006-06-16 6:51 ` Autoconf/Automake Nikolai Weibull
2006-06-15 20:10 ` Autoconf/Automake Phil Richards
2006-06-15 20:32 ` Autoconf/Automake Timo Hirvonen
2006-06-15 20:42 ` Autoconf/Automake Johannes Schindelin
2006-06-15 22:05 ` Autoconf/Automake Yann Dirson
2006-06-15 22:58 ` Autoconf/Automake Johannes Schindelin
2006-06-16 20:17 ` Autoconf/Automake Yann Dirson
2006-06-16 20:42 ` Autoconf/Automake Petr Baudis
2006-06-16 18:31 ` Autoconf/Automake Petr Baudis
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060615181922.GA36286@dspnet.fr.eu.org \
--to=galibert@pobox.com \
--cc=git@vger.kernel.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.
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 NNTP newsgroup(s).