Subject: Re: Repost, different list...File::Spec, cygwin, Syntactic vs. Semantic path analysis
From: "H.Merijn Brand" <[email-masked]>
To: Christopher Faylor <[email-masked]>
Cc: [email-masked], Perl 5 Porters <[email-masked]>
Date: Wed, 08 Jan 2003 15:30:25 +0100

On Wed 08 Jan 2003 05:56, Christopher Faylor <[email-masked]> wrote:
> >I'm sorry.  I thought the cygwin project -- was to provide a Posix type
> >platform to [aid, assist, help] in porting *nix/gnu utils to the Win32
> >environment.
> 
> Cygwin's primary purpose is to provide a UNIX environment for Windows.
> Although it can be used in other ways, the basic purpose is not to
> provide a stepping stone to helping port programs to native Windows.
> Things like Win32 path names and accommodating pure-win32 processes are
> *always* of secondary importance wrt getting the UNIX bits right.

Sorry to drop in like this, but how much influence do you have in Cygwin?
How much are you aware that 1.3.18-1 does fail in the current smokes where
1.3.16 passed? Gerrit seems to be quite busy these days.

Automated smoke report for patch 18456                               cc            gcc
                                                      | HP-UX 11.00  B.11.11.06    3.3   32-bit
O = OK                                                |                            3.3   64-bit +GNUld
F = Failure(s), extended report at the bottom         | HP-UX 10.20  A.10.32.30    3.2  
? = still running or test results not (yet) available | AIX 4.3.3.0  vac 5.0.2.6   3.1.1
Build failures during:       - = unknown,   = skipped | AIX 4.2.1.0  xlc 3.1.4.10  3.1.1
    c = Configure, m = make, t = make test-prep       | Cygwin 1.3.18              3.2-3

 HP-UX    HP-UX    HP-UX    HP-UX     AIX      AIX    cygwin  
 11.00    11.00    10.20    10.20    4.3.3    4.3.3   1.3.18-1  
  HPc      gcc      HPc      gcc      vac      gcc      gcc   
 18456    18456    18456    18456    18456    18453    18456   Configuration
-------  -------  -------  -------  -------  -------  -------  --------------------------------------------------------------------
O O O O  O O O O  O O O O  O O O O  O O O O  O O O O  F F F F   
O O O O  O O O O                    O O O O  O O O O  F F F F  -Duse64bitint
O O O O  O O O O                                      . . . .  -Duse64bitall
O O O O  O O O O  O O O O  O O O O  O O ? ?  O O O O  F F F F  -Duselongdouble
O O O O  O O O O                    ? ? ? ?           F F F F  -Dusemorebits
O O O O  O O O O                    ? ? ? ?           . . . .  -Duse64bitall -Duselongdouble
| |                            | |
| +----- PERLIO = perlio       | +- PERLIO = perlio -DDEBUGGING
+------- PERLIO = stdio        +--- PERLIO = stdio  -DDEBUGGING

Failures:

Cygwin 1.3   stdio             
Cygwin 1.3   stdio/perlio     -DDEBUGGING  
Cygwin 1.3   perlio           -Duse64bitint
Cygwin 1.3   stdio/perlio     -Duselongdouble
Cygwin 1.3   stdio            -Dusemorebits
    lib/IPC/Open3 ....................... 22
    lib/Test/Harness/t/strap-analyze .... 2
    lib/warnings ........................ 413-415
    t/op/alarm .......................... 1-4

Cygwin 1.3   perlio            
Cygwin 1.3   perlio           -Dusemorebits
Cygwin 1.3   stdio/perlio     -DDEBUGGING -Dusemorebits
    lib/IPC/Open3 ....................... 22
    lib/Test/Harness/t/strap-analyze .... 2
    lib/warnings ........................ 413-415

What's the stance of cygwin in threading?

-- 
H.Merijn Brand        Amsterdam Perl Mongers (http://amsterdam.pm.org/)
using perl-5.6.1, 5.8.0 & 633 on HP-UX 10.20 & 11.00, AIX 4.2, AIX 4.3,
  WinNT 4, Win2K pro & WinCE 2.11.  Smoking perl CORE: [email-masked]
http://archives.develooper.com/[email-masked]/   [email-masked]
send smoke reports to: [email-masked], QA: http://qa.perl.org

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/