Comment 4 for bug 1164056

Andrew

That would be fine. I need an excuse to upgrade. ;)

Mark

--
Sent from my Android phone with K-9 Mail. Please excuse my brevity and autocorrecter overzealousness.

Andrew Hutchings <email address hidden> wrote:

>I have been able to compile trunk in Fedora 18 (where we originally
>developed the mingw compiling) after fixing bug #1172010 (branch
>pending
>Jenkins testing before merging). I'll create a Fedora 14 VM next to
>try. I should note though that Fedora 14 is past EOL so we may not be
>able to support it. I don't know if anyone has tried compiling using
>Windows yet, I should be able to test that too this week.
>
>--
>You received this bug notification because you are subscribed to the
>bug
>report.
>https://bugs.launchpad.net/bugs/1164056
>
>Title:
> Error compiling in MinGW
>
>Status in Drizzle Client & Protocol Library:
> Triaged
>
>Bug description:
> I'm attempting to compile 5.1.3 on a MinGW platform and I get the
> following:
>
> In file included from ./libdrizzle/common.h:55:0,
> from libdrizzle/command.cc:46:
> ./libdrizzle/windows.hpp: In function 'int translate_windows_error()':
>./libdrizzle/windows.hpp:85:18: error: 'EINPROGRESS' was not declared
>in this scope
>./libdrizzle/windows.hpp:93:18: error: 'ECONNREFUSED' was not declared
>in this scope
>./libdrizzle/windows.hpp:97:18: error: 'ENETUNREACH' was not declared
>in this scope
>./libdrizzle/windows.hpp:101:18: error: 'ETIMEDOUT' was not declared in
>this scope
>./libdrizzle/windows.hpp:105:18: error: 'ECONNRESET' was not declared
>in this scope
>./libdrizzle/windows.hpp:109:18: error: 'EADDRINUSE' was not declared
>in this scope
>./libdrizzle/windows.hpp:113:18: error: 'EOPNOTSUPP' was not declared
>in this scope
>./libdrizzle/windows.hpp:117:18: error: 'ENOPROTOOPT' was not declared
>in this scope
> make[1]: *** [libdrizzle/libdrizzle_libdrizzle_la-command.lo] Error 1
> make[1]: Leaving directory `/home/backuppc/schematic/libdrizzle-5.1.3'
> make: *** [all] Error 2
>
> I read that a patch to solve this was supposed to have been merged. Do
> the patches still need to be merged? I honestly haven't been able to
> dig any further as I've been tied up in other fires but it would be
> nice to get a fix for this one.
>
> In addition to 5.1.3 I've also retrieved the latest code from the
> codestore in the chance that patches have been applied and not
> released as a tar.gz file. It too exhibits the above output.
>
> Mark
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/libdrizzle/+bug/1164056/+subscriptions