"Akim" == Akim Demaille [EMAIL PROTECTED] writes:
Akim Have you given a try to my suggestion of
Akim if (PATH=.;`pwd`; conftest.sh); then
Arg, of course you didn't...
From: Mail Delivery System Mailer-Daemon@=
Subject: Mail delivery failed: returning message to sender
To: akim@=
X-Sent: 5
"Tim" == Tim Van Holder [EMAIL PROTECTED] writes:
Tim I suppose so. My main point was that there were 2 different
Tim issues related to path separators (build _HOST_), which the PR
Tim didn't seem to take into account.
Personally, at least for the time being, we don't care about HOST: as
said
"Mark" == Mark E [EMAIL PROTECTED] writes:
I'd like to advise you that it would be fair not to support
non-UNIX path separators on the build system.
Mark Naturally, I'll have to disagree. I don't see why Autoconf
Mark should care which path separator is used as long as Autoconf can
Mark
Akim Demaille wrote:
"Tim" == Tim Van Holder [EMAIL PROTECTED] writes:
Tim I suppose so. My main point was that there were 2 different
Tim issues related to path separators (build _HOST_), which the PR
Tim didn't seem to take into account.
Personally, at least for the time being, we
On Jan 30, 2001, Akim Demaille [EMAIL PROTECTED] wrote:
if (PATH=.;`pwd`; conftest.sh); then
# We like `;', let's use it.
else if (PATH=.:`pwd`; conftest.sh); then
# We like `:', let's use it.
else
# Get lost.
fi
Hmm... It's just occurred to me that this kind of test may not work
"Alexandre" == Alexandre Oliva [EMAIL PROTECTED] writes:
Alexandre Hmm... It's just occurred to me that this kind of test may
Alexandre not work in general. AFAIK, some old Unices just won't run
Alexandre shell-scripts like that; you have to explicitly specify the
Alexandre shell that must
On Jan 31, 2001, Akim Demaille [EMAIL PROTECTED] wrote:
It seems to me that falling to `:' is way enough for this case.
I hope so.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student
DOES pretend to do)? DJGPP can pretend to be unixy when it comes to pathseps,
but ONLY inside bash (granted, that's where it will matter most, but using ':'
because bash can handle it would break if used inside perl/m4/whatever).
Since the test is run by bash and not by something else it
cat EOF conftest.sh
#! $SHELL
exit 0
EOF
chmod +x conftest.sh
if (PATH=.;`pwd`; conftest.sh); then
# We like `;', let's use it.
Slackware will like it :-)
It already has "." in $PATH for non-root users.
I don't see an alternative to using a separate directory.
But you conftest.sh is
It's not called TARGET. It's called HOST. TARGET is only meaningful for
compilers and other tools working together to create executables _for_ a
particular platform.
OK - my bad.
I'd like to advise you that it would be fair not to support non-UNIX path
separators on the build system.
I'd like to advise you that it would be fair not to support non-UNIX path
separators on the build system. Autoconf doesn't pretend to support such
systems.
Then what's the point of supporting DJGPP, OS/2 or Mingw32 (which autoconf
I understand that Mingw32 is supported with the Cygwin's
11 matches
Mail list logo
