mingw-cross-env-list
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Mingw-cross-env-list] Postgresql build broken?


From: Tony Theodore
Subject: Re: [Mingw-cross-env-list] Postgresql build broken?
Date: Mon, 7 Feb 2011 02:15:33 +1100

On 6 February 2011 11:47, René Berber <address@hidden> wrote:
> Hi,
>
> While rebuilding Qt I found that PostgreSQL no longer builds, the
> problem is in PostgreSQL, it defines:
>
> include/port/win32.h:#define ftruncate(a,b)       chsize(a,b)
>
> which causes the problem, which is this conflict:
>
> In file included from fe-connect.c:23:0:
> /export/home/rberber/mingw-cross-env/usr/bin/../lib/gcc/i686-pc-mingw32/4.5.2/../../../../i686-pc-mingw32/include/unistd.h:41:5:
> error: conflicting types for 'chsize'
> /export/home/rberber/mingw-cross-env/usr/bin/../lib/gcc/i686-pc-mingw32/4.5.2/../../../../i686-pc-mingw32/include/io.h:442:63:
> note: previous declaration of 'chsize' was here
>
> In short, io.h defines function int chsize(int, long) while unistd.h
> defines int ftruncate(int, off_t) and the macro takes care of messing
> everything up.
>
> First point: does PostgreSQL even need to re-define ftruncate?

Hard to say, a brief search indicates that mingw implemented this and
some other fs functions rather than using the win APIs, maybe the
postgres team wanted to do it differently?

> Second: is it me or everyone else has this problem?  It seems strange
> that Postgresql was building fine until this week (I even tried rolling
> back the .mk file, same problem with previous version).

I don't have an issue here, can you send the log file?

Cheers,

Tony



reply via email to

[Prev in Thread] Current Thread [Next in Thread]