From: Dennis Stosberg <dennis@stosberg.net>
To: Timo Hirvonen <tihirvon@gmail.com>
Cc: Matthias Lederhofer <matled@gmx.net>, git@vger.kernel.org
Subject: Re: [PATCH 1/3] configure: Add test for Perl
Date: Thu, 6 Jul 2006 17:34:45 +0200 [thread overview]
Message-ID: <20060706153445.G424b7ea1@leonov.stosberg.net> (raw)
In-Reply-To: <20060706172756.a42f1627.tihirvon@gmail.com>
Timo Hirvonen wrote:
> if test -x "$1"
> then
> echo "$1"
> return 0
> fi
When run in the Git source directory, this will find the perl/
subdir. If the user gives an absolute path to the perl binary,
there will be no auto-detection anyway, so I think we don't need it.
> It is not needed but might be useful if PERL is user configurable
> variable and can contain either full path or basename. For example this
> code
>
> test "$PROG" || PROG=prog
> PROG=`path_find "$PROG"`
>
> works with these cases
>
> $ PROG=/usr/bin/program ./configure
> $ PROG=program-1.2 ./configure
I will add that. For the compiler, the script already checks $CC.
I wonder whether
--with-perl=...
--with-python=...
is more common (more similar to autoconf) than
--perl=
--python=
Regards,
Dennis
next prev parent reply other threads:[~2006-07-06 15:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 12:40 [PATCH 1/3] configure: Add test for Perl Dennis Stosberg
2006-07-06 13:03 ` Randal L. Schwartz
2006-07-06 13:10 ` Timo Hirvonen
2006-07-06 13:29 ` Dennis Stosberg
2006-07-06 13:58 ` Matthias Lederhofer
2006-07-06 14:17 ` Gerrit Pape
2006-07-06 14:25 ` Dennis Stosberg
2006-07-06 14:27 ` Timo Hirvonen
2006-07-06 15:34 ` Dennis Stosberg [this message]
2006-07-07 11:06 ` Petr Baudis
2006-07-07 11:20 ` Junio C Hamano
2006-07-07 11:23 ` Timo Hirvonen
2006-07-06 15:40 ` Alex Riesen
2006-07-06 15:44 ` Dennis Stosberg
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=20060706153445.G424b7ea1@leonov.stosberg.net \
--to=dennis@stosberg.net \
--cc=git@vger.kernel.org \
--cc=matled@gmx.net \
--cc=tihirvon@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.
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).