On 08/16/2013 02:12 AM, Albe Laurenz wrote:
Yes, any patches should be posted to -hackers, in this case
with a archive reference to the discussion on -general.
Please readhttp://wiki.postgresql.org/wiki/Submitting_a_Patch
To make sure that the patch does not get lost, add it to
the next commitf
Michael Cronenworth wrote:
> On 08/15/2013 10:59 AM, Michael Cronenworth wrote:
> > The attached patches resolve the issue.
>
> Should I forward the patches on to the pgsql-hackers list for review or is
> this
> list sufficient? (First time PostgreSQL hacker.)
Yes, any patches should be posted t
On 08/15/2013 10:59 AM, Michael Cronenworth wrote:
> The attached patches resolve the issue.
Should I forward the patches on to the pgsql-hackers list for review or is this
list sufficient? (First time PostgreSQL hacker.)
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To
On 08/13/2013 12:35 PM, Michael Cronenworth wrote:
> When the client library (version 9.2.x) is compiled with a MinGW-w64
> environment
> the resulting libpq.dll will not function. This has been reported previously
> with two bug reports, which have gone untouched.
>
> Bug 8151:
> http://www.post
On 08/14/2013 08:57 AM, John R Pierce wrote:
>
> no. GCC uses a totally different libc in its generated code. that alone
> ensures its binaries are not directly comparable.linking code with
> incompatible libc's is gonna result in some gnarly messes, imagine what
> kind of ugly stuff could ha
On 8/13/2013 2:25 PM, Michael Cronenworth wrote:
On 08/13/2013 01:40 PM, John R Pierce wrote:
>They use Microsoft Visual C (I forget the exact version, but I believe most
>recent versions are supported, including the "Express" versions).
Then MinGW should be capable of producing the same binari
On 8/13/2013 5:25 PM, Michael Cronenworth wrote:
On 08/13/2013 01:40 PM, John R Pierce wrote:
They use Microsoft Visual C (I forget the exact version, but I believe most
recent versions are supported, including the "Express" versions).
Then MinGW should be capable of producing the same binarie
On 08/13/2013 01:40 PM, John R Pierce wrote:
> They use Microsoft Visual C (I forget the exact version, but I believe most
> recent versions are supported, including the "Express" versions).
Then MinGW should be capable of producing the same binaries.
I've tried early gcc 4.7 and the latest gcc 4
On 8/13/2013 10:35 AM, Michael Cronenworth wrote:
What environment does EnterpriseDB use to create their Windows binaries?
They use Microsoft Visual C (I forget the exact version, but I believe
most recent versions are supported, including the "Express" versions).
--
john r pierce
