$ eval 'echo toto >/tmp/stdout 2>/tmp/stderr' >/tmp/outter
illegal io
$
Could you try this?
eval '(echo toto >/tmp/stdout 2>/tmp/stderr)' >/tmp/outter
$ eval 'echo toto >/tmp/stdout 2>/tmp/stderr'
$ cat /tmp/stdout
toto
$ cat /tmp/stderr
$
$ eval 'echo toto >/tmp/stdout 2>/tmp/stderr' >/tmp/outter
illegal io
$
Thanks Harlan!
$ eval 'echo toto >/tmp/stdout 2>/tmp/stderr'
$ cat /tmp/stdout
toto
$ cat /tmp/stderr
$
$ eval 'echo toto >/tmp/stdout 2>/tmp/stderr' >/tmp/outter
illegal io
$
Harlan
> Could you try this?
>
> eval 'echo toto >/tmp/stdout 2>/tmp/stderr'
>
> and
>
> eval 'echo toto >/tmp/stdout 2>/tmp/stderr
Could you try this?
eval 'echo toto >/tmp/stdout 2>/tmp/stderr'
and
eval 'echo toto >/tmp/stdout 2>/tmp/stderr' >/tmp/outter
?
Thanks!
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Harlan> checking whether build environment is sane... yes
Harlan> /bin/sh: \272: not found
Alexandre> What if you take the quotes off "$prog" ?
Harlan> That seems to be the ticket!
Warf warf warf!
272 = 200 (8th bit) + 72 (ascii
> What if you take the quotes off "$prog" ?
That seems to be the ticket!
I'm running the new script on a number of platforms just to be sure.
H
On Dec 29, 2000, Harlan Stenn <[EMAIL PROTECTED]> wrote:
> Still doesn't work, and should the second problem be forked into a thread
> for autoconf while this one stays on automake?
Yep, the latter is certainly a problem in autoconf.
What if you take the quotes off "$prog" ?
--
Alexandre Oliv
On that second problem, a fragment of config.log follows:
...
configure:1867: checking whether gcc accepts -g
configure:1885: gcc -c -g conftest.c >&5
configure:1888: $? = 0
configure:1899: result: yes
configure:1924: checking how to run the C preprocessor
configure:1948: gcc -E conftest
> > + eval ${SHELL} /pogo/users/stenn/src/ntp.001227/missing --run :
>
> I believe this can't be a problem in autoconf, since the `missing'
> script is maintained as part of automake and, indeed, the test to
> check whether it supports the `--run' switch relies upon `:'.
>
> Does missing work
On Dec 29, 2000, Harlan Stenn <[EMAIL PROTECTED]> wrote:
> + eval ${SHELL} /pogo/users/stenn/src/ntp.001227/missing --run :
I believe this can't be a problem in autoconf, since the `missing'
script is maintained as part of automake and, indeed, the test to
check whether it supports the `--run'
While tracking down the apparent non-problem with OBJEXT I followed
somebody's advice and ran the "configure" step under "sh -x", which produced
the following output on the Ultrix box:
...
MISSING=${SHELL} /pogo/users/stenn/src/ntp.001227/missing
+ eval ${SHELL} /pogo/users/stenn/src/ntp.00122
Harlan Stenn wrote:
> /bin/sh: : not found
> WARNING: `:' is needed, and you do not seem to have it handy on your
> system. You might have modified some files without having the
> proper tools for further handling them. Check the `README' file,
> it often tells you
12 matches
Mail list logo