> Date: Thu, 20 Jan 2005 12:35:08 +0100
> From: Stepan Kasal <[EMAIL PROTECTED]>
> Cc: Eric Blake <[EMAIL PROTECTED]>, autoconf@gnu.org, bug-texinfo@gnu.org
>
> The trick is that AC_CHECK_PROG contains the following code:
>
> for ac_exec_ext in '' $ac_executable_extensions; do
> if AS_EXECUTABL
Hi,
On Thu, Jan 20, 2005 at 04:42:24PM -0800, Paul Eggert wrote:
> > 2) The autoconf manual says you cannot use `test ! -d' with `if'.
>
> Where does it say that? I couldn't find it.
under the description of bultin `test',
line 11085 of doc/autoconf.texi, currently.
Stepan
__
Hi,
On Fri, Jan 21, 2005 at 04:21:44AM +0100, Ralf Corsepius wrote:
> How about portability of "test -d" being applied to "special
> files" (char/block device files, pipes/sockets, soft/hard links to
> directories/files etc.)?
so the question is:
If I change AS_EXECUTABLE_P the proposed way, it
* Stepan Kasal wrote on Fri, Jan 21, 2005 at 11:20:03AM CET:
>
> On Thu, Jan 20, 2005 at 04:42:24PM -0800, Paul Eggert wrote:
> > > 2) The autoconf manual says you cannot use `test ! -d' with `if'.
> >
> > Where does it say that? I couldn't find it.
>
> under the description of bultin `test',
>
Hi,
On Fri, Jan 21, 2005 at 11:54:45AM +0100, Ralf Wildenhues wrote:
> * Stepan Kasal wrote:
> > 2) The autoconf manual says you cannot use `test ! -d' with `if'.
...
> | You may use @samp{!} with @command{test}, but not with @command{if}:
> | @samp{test ! -r foo || exit 1}.
>
> means that you ma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> But this may cause problems on MS-DOS derivations.
> Lets suppose that we have a file named foo.exe, but not foo.
> Both DJGPP and Cygwin have extensions which cause `test -x foo' to succeed.
> But `test -f' fails, so the whole AS_EXECUTABLE_P(foo) f
Hi,
On Fri, Jan 21, 2005 at 07:17:17AM -0700, Eric Blake wrote:
> Actually, `test -f foo' only fails on foo.exe on DJGPP (at least,
> according to claims - I don't have a DJGPP environment to test on) - it
> works on cygwin.
anyway, it seems that changing AS_EXECUTABLE_P from
test -f $1
Stepan Kasal <[EMAIL PROTECTED]> writes:
> it seems that changing AS_EXECUTABLE_P from
>
> test -f $1 && test -x $1
>
> to
> test -x $1 && test ! -d $1
>
> might please the DJGPP people.
>
> Does it hust someone else?
Yes. For example, it won't work on the following files on my Solar
Stepan Kasal <[EMAIL PROTECTED]> writes:
> The item about `!' mentions the following code:
>
> if @var{command}; then (exit 1); else :; fi
>
> Can I change the suggestion to
>
> if @var{command}; then false; else :; fi
>
> Yes, the exit code might be 255, but it shouldn't matter.
The
> From: Ben Pfaff <[EMAIL PROTECTED]>
> Date: Thu, 20 Jan 2005 13:30:27 -0800
> Cc: autoconf@gnu.org
>
> >>test -f tex.exe && test -x tex.exe
> >
> > This will work, but is redundant: it's enough to test for tex.exe,
> > since it's always executable on MS systems.
>
> I have had Windows syste
"Eli Zaretskii" <[EMAIL PROTECTED]> writes:
>> From: Ben Pfaff <[EMAIL PROTECTED]>
>> Date: Thu, 20 Jan 2005 13:30:27 -0800
>> Cc: autoconf@gnu.org
>>
>> >> test -f tex.exe && test -x tex.exe
>> >
>> > This will work, but is redundant: it's enough to test for tex.exe,
>> > since it's always exe
11 matches
Mail list logo
