Skip site navigation (1) Skip section navigation (2)

Re: Compilations failing

From: "Jeroen T(dot) Vermeulen" <jtv(at)xs4all(dot)nl>
To: "Andreas Gidlund" <vaxis(at)hotmail(dot)com>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: Compilations failing
Date: 2006-10-02 06:51:38
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
On Mon, October 2, 2006 02:36, Andreas Gidlund wrote:

> it will stop when
> compiling \src\backend\utils\mb\wchar.c, because there are two functions
> which cannot be compiled, pg_euc_mblen and pg_euc_dsplen. The reason is
> that
> they are declared both static and inlined, which is a syntax nmake
> appearantly does not support.

That's not nmake; that's the compiler.  The combination of "inline static"
sounds perfectly valid to me though--don't see why that would be a
problem.  Perhaps it's a simple matter of "static inline" vs. "inline

> Though, here comes a problem. When I tried to execute a query and hence
> recieve the result into a PGresult, the compiler complains about that the
> variable uses an undefined struct, pg_result.

That's odd...  Are you compiling postgres as "managed code," by any
chance?  That would explain runtime errors of this kind (which in C and
C++ should give you compile-time errors or just work), and it's also known
to cause lots of confusion and link errors with libpqxx.

The problem with "managed code" is that it's not really compatible with
C++, but this fact is apparently not made very obvious.  From what I hear,
the code can look similar but it's not possible to link "managed C++" to
C++ DLLs.  The situation with C may be similar.


In response to

pgsql-interfaces by date

Next:From: Andreas GidlundDate: 2006-10-09 14:58:05
Subject: Retrieve all the returned rows in one call
Previous:From: Andreas GidlundDate: 2006-10-01 19:36:56
Subject: Re: Compilations failing

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group