in reply to Re: Re: Re: colons don't always separate path items!
in thread colons don't always separate path items!

And I get a program named diff where...? Not just any program named diff.exe, but one that outputs the stuff p5p expects.

—John

Replies are listed 'Best First'.
Re: Re: Re: Re: Re: colons don't always separate path items!
by demerphq (Chancellor) on Jul 02, 2003 at 12:22 UTC

    www.cygwin.com for Win32.


    ---
    demerphq

    <Elian> And I do take a kind of perverse pleasure in having an OO assembly language...
      I avoid cygwin-compiled stuff because it doesn't like normal path names. I have to change all drive letters to its own "mount point" things.

        Actually this only applies to small handfull of the cygwin tools. And diff isnt one of them :-) It works just peachy under cmd.exe and doesnt choke on real win32 paths.

        However ive encountered this annoyance before myself. Iirc gzip and tar suffer from this problem. But most of them dont. (Although be careful with tail, it can cause Win2k to spontaneously reboot (no BSOD or anything!) if another process uses win32 directory change events on the same file as is being tailed.)
        ---
        demerphq

        <Elian> And I do take a kind of perverse pleasure in having an OO assembly language...

Re: Re: Re: Re: Re: colons don't always separate path items!
by PodMaster (Abbot) on Jul 02, 2003 at 05:16 UTC
    http://www.mingw.org/ is one place. Got a CVS client? diff should come with it used to come with some.

    update: "GnuWin32 provides Win32 (MS Windows 95 / 98 / ME / NT / 2000 / XP) ports of tools with a GNU or similar open source license. "

    MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
    I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
    ** The third rule of perl club is a statement of fact: pod is sexy.