[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MinGW vs. c-api.test

From: Ludovic Courtès
Subject: Re: MinGW vs. c-api.test
Date: Tue, 10 Jun 2014 13:44:17 +0200
User-agent: Gnus/5.130009 (Ma Gnus v0.9) Emacs/24.3 (gnu/linux)

address@hidden (Ludovic Courtès) skribis:

> Eli Zaretskii <address@hidden> skribis:
>> 2. c-api.test fails with many messages such as this one:
>>      'CUR' is not recognized as an internal or external command,
>>      operable program or batch file.
>>    This is because c-api.test does this:
>>      (define (egrep string filename)
>>        (zero? (system (string-append "egrep '" string "' " filename " 
>> >/dev/null"))))
>>      ...
>>               (if (and (file-exists? file)
>>                        (egrep "SEEK_(SET|CUR|END)" file))
>>    There are two problems here: quoting that is not supported by
>>    Windows shells, and redirection to /dev/null.  The former is easily
>>    fixed portably:
>>      (system (string-append "egrep \"" string \"" " filename
>>    The latter requires either an OS-dependent string in the *.scm
>>    source of the test, or a variable (called, e.g., null-device) that
>>    will be set correctly for each platform, which could then be used
>>    by the test unconditionally.

Eli, I noticed there are many other occurrences of /dev/null in the test
suite.  Do they all need to be patched to use NUL, or is /dev/null
somehow interpreted correctly in some contexts?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]