[DGD] DGD For MSys, mark 2

[Jared Maddox]

Sorry about the delay, stuff came up.

> Date: Tue, 08 Jan 2013 14:44:22 +0100
> From: "Felix A. Croes" <felix at dworkin.nl>
> To: dgd at dworkin.nl
> Subject: Re: [DGD] DGD For MSys, mark 2
> Message-ID: <E1TsZTa-0003Us-4I at pattern>
>
> Jared Maddox <absinthdraco at gmail.com> wrote:
>

>>[...]
>> As for the OS detection code, it was specifically returning the
>> specific version of Windows that I run (XP). Suffice to say, that's a
>> bit more platform-specific than I was looking at. At the same time, I
>> wanted to print an informative error message if someone tried to use a
>> mingw/msys make from the Windows command line, since uname is almost
>> universally not available on Windows.
>
> Isn't uname included with msys?
>

uname is included with MSys, but MinGW (which is the compiler
component of MSys) is actually stand-alone, and includes it's own
make. Since this means that a GNU make is available natively for
Windows from the very project that I'm trying to support, I'd like to
at least have an error message if someone tries to use it. The exact
method doesn't worry me too much though, so I can try to dig up
another route to that warning. I think that the MSys mailing list
mentioned how to detect that specific version of make.

>>[...]
>> >> Should the "HOST_OVERRIDE" switch be enough for any other *nix-ish
>> >> platforms on Windows?
>> >
>> > Due to the automatic import of environment variables into GNU Make,
>> > depending on a predefined symbol is a bad idea.
>> >
>>
>> I'm challenged to think of another way to do it, though (thinking
>> about it, I should at least name it DGD_TARGETHOST). Do you know of
>> any better methods?
>
> If I wanted to get this to work on other pseudo-unix platforms, I would
> either try to detect those platforms, or make it easy to add them later.
> HOST_OVERRIDE is just a messy shortcut.
>

Ok. I half-added it to try to get some people who wanted me to rework
the build system into an autoconf setup to drop the subject anyways.

>>[...]
>> Nope, same problem. On Firefox 17.0.1:
>>
>> Secure Connection Failed
>> An error occurred during a connection to mail.dworkin.nl.
>> Peer reports incompatible or unsupported protocol version.
>
> Sounds like TLS support is not turned on in your browser (it's on the
> preferences/advanced/encryption page).
>

Thanks, I hadn't realized that it was disabled.