Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 60E1D9FB993 for ; Thu, 5 Jul 2007 21:39:34 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 68909-03 for ; Thu, 5 Jul 2007 21:39:28 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226]) by postgresql.org (Postfix) with ESMTP id 8B0DF9FB929 for ; Thu, 5 Jul 2007 21:39:28 -0300 (ADT) Received: from dynamic.hagander.net ([127.0.0.1]) (encrypted and authenticated) by svr2.hagander.net (Postfix) with ESMTP id DE316DCCB8C; Fri, 6 Jul 2007 02:39:25 +0200 (CEST) Message-ID: <468C7D67.3090509@hagander.net> Date: Thu, 05 Jul 2007 07:11:03 +0200 From: Magnus Hagander User-Agent: Thunderbird 2.0.0.5pre (Windows/20070704) MIME-Version: 1.0 To: Phil Mills CC: pgsql-ports@postgresql.org Subject: Re: Compilation failure: 8.2.4 and 8.1.0 under XPPro/MinGW References: <5C45D12040C19D439DA0CE63A18738063399FF@ftcexch2.int.veeco.com> In-Reply-To: <5C45D12040C19D439DA0CE63A18738063399FF@ftcexch2.int.veeco.com> X-Enigmail-Version: 0.95.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/4 X-Sequence-Number: 2563 Phil Mills wrote: > I've seen the build error below referenced in several messages, but haven't seen a clear answer for how to resolve it. > > Environment: XP Pro with MSys/MinGW freshly installed according to the docs here: http://www.postgresql.org/docs/faqs.FAQ_MINGW.html > Zlib is installed; Visual Studio and Cygwin are also on the system but should be out of the way. > > Reason for building: increase NAMEDATALEN so it'll quit truncating my absurdly-large column names. > > Output from Make (substantially the same whether I'm building 8.2.4 or 8.1.0): This means your MingW is too new :-O They made an incompatible change to their headers at some point (I think someone said you need 3.9 or earlier). So your workaround is to downgrade to an older version of mingw. (Or do the manual header hackery that someone posted, but I'd really recommend something that works without changing the libc headers) Now that I see it again, I do think I have a patch sitting around somewhere to fix that, I guess I'll have to find and review that one. If we can't fix it, we at least need to get it into the FAQ. I'll write up a suggestion for text there if I can't get the code fixed. Unfortunately, keeping up with mingw is developing against a moving target, so these things happen :-( //Magnus