So my guess is that you don't run GNU sed. I don't know too well what
to do wrt this issue.
Every DOS utility I have is GNU, including sed.
Have autoupdate use Perl?
Sorry, I don't understand the question.
| I don't get it at all. Why would you have such problems, and I
| don't???
|
| The problem went away after the latest cvs update. I still get one failure,
| but I see nothing as of yet that would classify it as DOS-specific.
Good to know.
| =
|
| + ../autoupdate -m .. -
| c:/djgpp/tmp/au16317/input.m4:44: c:/djgpp/bin/m4.exe: Cannot open
| [c:/djgpp/tmp/au16317/m4.m4]: No such file or directory (ENOENT)
| c:/djgpp/tmp/au16317/input.m4:44: c:/djgpp/bin/m4.exe: Cannot open
|
| After playing with generated temporary files, it seems
I don't get it at all. Why would you have such problems, and I
don't???
The problem went away after the latest cvs update. I still get one failure,
but I see nothing as of yet that would classify it as DOS-specific.
=
./debug-98.sh: Testing autoupdate
+ ../autoupdate -m .. -
c:/djgpp/tmp/au16317/input.m4:44: c:/djgpp/bin/m4.exe: Cannot open
[c:/djgpp/tmp/au16317/m4.m4]: No such file or directory (ENOENT)
c:/djgpp/tmp/au16317/input.m4:44: c:/djgpp/bin/m4.exe: Cannot open
After playing with generated temporary files, it seems like a
| Could you give more details on these steps? What can be done to have
| it right without tuning by hand?
|
| What I set is:
| PATH_SEPARATOR=:
| TEST_FINDS_EXE=Y
Wow, are you telling us we no longer need to dive into `test $ac_x'
and things like this?
| CC=gcc
That's a known problem of
| TEST_FINDS_EXE=Y
Wow, are you telling us we no longer need to dive into `test $ac_x'
and things like this?
It's a solution designed so we don't have to modify configure scripts, but
it's a hack. And it's a DJGPP-only solution, so it doesn't help EMX or any
other similiar environment .
"Mark" == Mark E [EMAIL PROTECTED] writes:
| TEST_FINDS_EXE=Y
Wow, are you telling us we no longer need to dive into `test $ac_x'
and things like this?
Mark It's a solution designed so we don't have to modify configure
Mark scripts, but it's a hack. And it's a DJGPP-only solution, so it
OK, so we must start working on this.
A unified solution is certainly desirable. But perhaps we should find out how
urgent a solution to this problem is before you decide to take on this
problem for the next release. DJGPP's Bash has a solution (TEST_FINDS_EXE as
mentioned), Cygwin (I've
--- Akim Demaille [EMAIL PROTECTED] wrote:
-8-
But after all, maybe just basing our decisions on uname is enough.
Yes, this is against the philosophy of Autoconf, but it's better than
nothing. And I guess we don't have to fear portability problems with
uname, since I suppose the environments
--- "Mark E." [EMAIL PROTECTED] wrote:
other similiar environment . My preference would be to test for programs
using 'prog_to_find${ac_exeext}'. Then somehow figure out when ${ac_exeext}
needs to be set without resorting to compiling a program.
or at least allow it be set in
Seeing as how Akim wants DJGPP to pass the testsuite, I figure it would be a
good idea report my initial results using DJGPP and Autoconf from CVS.
After setting some environment variables (CC, etc.) and correcting a DJGPP
specific bug in Bash 2.04, the test went well with one minor and one
12 matches
Mail list logo
