Hi Dan,

On Fre 13.06.2008 14:35, Dan Fandrich wrote:
>On Fri, Jun 13, 2008 at 11:04:24PM +0200, Aleksandar Lazic wrote:

[snipp]

>> test 1004...[HTTP GET with empty proxy]
>> ../src/curl --output log/curl1004.out --include -v --trace-time \
>> http://127.0.0.1:8990/1004 --proxy "" >>log/stdout1004 \
>> 2>>log/stderr1004
>
>This is an odd result. What appears to be happening is that the test
>harness executes this curl command, but it's interpreted by curl as
>though the empty "" string after --proxy isn't there, i.e. the command
>actually run is this:
>
> ../src/curl --output log/curl1004.out --include -v --trace-time
> http://127.0.0.1:8990/1004 --proxy >>log/stdout1004 2>>log/stderr1004

>
>which results in a curl error and failure of the test case.
>
>Can you track down why this happens on your machine? The command is
>run at line 2089 of tests/runtests.pl which eventually just uses perl's
>system() call on the string. You could also try replacing the "" with
>'' in the tests/data/test1004 file which could help indicate if it's a
>weird quoting problem. If you could somehow force perl to use a
>different shell to execute the command (maybe /bin/ksh instead of
>/bin/sh) it would help trace it to a shell problem.

the change from " to ' haven't change anything.
Attached the perl -V output, maybe some of the patches produce this
error?

Aleks