<div dir="ltr">I see the port.h also present in the postgresql-server-dev package. Here is the list:<div><br></div><div><a href="http://packages.debian.org/sid/i386/postgresql-server-dev-9.3/filelist">http://packages.debian.org/sid/i386/postgresql-server-dev-9.3/filelist</a></div>
<div><br></div><div>if you build the sources, you will find port.h always in server include.<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Dec 11, 2013 at 9:28 PM, Steve Singer <span dir="ltr"><<a href="mailto:ssinger@ca.afilias.info" target="_blank">ssinger@ca.afilias.info</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="im">On 12/11/2013 05:14 AM, Sandeep Thakkar wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
How did you install postgresql on Debian? I have built PosrgreSQL<br>
sources on CentOS, OSX and Windows and the port.h is installed in<br>
include/postgresql/server/<u></u>port.h and include/postgresql/internal/<u></u>port.h<br>
on all platforms.<br>
</blockquote>
<br>
<br></div>
The packages from <a href="http://apt.postgresql.org" target="_blank">apt.postgresql.org</a><br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="im">
<br>
<br>
On Sun, Dec 8, 2013 at 9:40 AM, Steve Singer <<a href="mailto:ssinger@ca.afilias.info" target="_blank">ssinger@ca.afilias.info</a><br></div><div class="im">
<mailto:<a href="mailto:ssinger@ca.afilias.info" target="_blank">ssinger@ca.afilias.<u></u>info</a>>> wrote:<br>
<br>
On 11/29/2013 04:30 AM, Sandeep Thakkar wrote:<br>
<br>
The only work around I see now if to set the CPPFLAGS in the<br>
environment<br>
to the server include directory, so that CPPFLAGS_CLIENT takes<br>
it in the<br>
Makefile.global.<br>
<br>
<br>
<br>
So in debian (or at least with Wheezy) where the original bug 315<br>
was reported<br>
<br>
<br>
libpq-dev puts port.h in /usr/include/postgresql/port.h so it gets<br>
picked up by the client include paths. I am able to do a build with<br>
--with-pgport<br>
<br>
This isn't actually a problem on debian, is the problem on OSX that<br>
port.h isn't being put in the libpq header directories? Should it?<br>
Where do other platforms/distributions put port.h ?<br>
<br>
<br>
<br>
On Tue, Nov 26, 2013 at 7:05 PM, Steve Singer<br>
<<a href="mailto:ssinger@ca.afilias.info" target="_blank">ssinger@ca.afilias.info</a> <mailto:<a href="mailto:ssinger@ca.afilias.info" target="_blank">ssinger@ca.afilias.<u></u>info</a>><br></div>
<mailto:<a href="mailto:ssinger@ca.afilias." target="_blank">ssinger@ca.afilias.</a>__<u></u>info<div class="im"><br>
<mailto:<a href="mailto:ssinger@ca.afilias.info" target="_blank">ssinger@ca.afilias.<u></u>info</a>>>> wrote:<br>
<br>
On 11/26/2013 04:14 AM, Sandeep Thakkar wrote:<br>
<br>
Hi<br>
<br>
I was building Slony1-2.2.1 sources on Mac OS X and<br>
found that<br>
the build<br>
fails because of:<br>
<br>
slonik.c:49:18: error: port.h: No such file or directory<br>
CPPFLAGS is now defined to just CPPFLAGS_CLIENT that<br>
does not<br>
include<br>
the PG "server" include directory<br></div>
('<pginstall>/include/____<u></u>postgresql/server' contains<div class="im"><br>
port.h). Any<br>
<br>
specific<br>
reason why this change was made in 2.2.1?<br>
<br>
<br>
<br></div>
<a href="http://www.slony.info/____bugzilla/show_bug.cgi?id=315" target="_blank">http://www.slony.info/____<u></u>bugzilla/show_bug.cgi?id=315</a><br>
<<a href="http://www.slony.info/__bugzilla/show_bug.cgi?id=315" target="_blank">http://www.slony.info/__<u></u>bugzilla/show_bug.cgi?id=315</a>><div class="im"><br>
<br>
<<a href="http://www.slony.info/__bugzilla/show_bug.cgi?id=315" target="_blank">http://www.slony.info/__<u></u>bugzilla/show_bug.cgi?id=315</a><br>
<<a href="http://www.slony.info/bugzilla/show_bug.cgi?id=315" target="_blank">http://www.slony.info/<u></u>bugzilla/show_bug.cgi?id=315</a>>><br>
<br>
On systems that have multiple versions of postgresql<br>
installed might<br>
pull in files for the client from one version and server<br>
includes<br>
from another. You used to be able to get away with this<br>
but in more<br>
recent versions of PG this breaks things.<br>
<br>
I am not exactly sure what the best way to deal with this<br>
in the<br>
PGPORT case? I have a feeling just adding the server<br>
includes back<br>
in on --with-pgport builds will get us back to the bug 315<br>
situation<br>
<br>
<br>
<br>
<br>
<br>
--<br>
Sandeep Thakkar<br>
<br>
<br></div>
______________________________<u></u>_____________________<br>
Slony1-general mailing list<br>
Slony1-general@lists.slony.___<u></u>_info<br>
<mailto:<a href="mailto:Slony1-general@lists." target="_blank">Slony1-general@lists.</a>_<u></u>_<a href="http://slony.info" target="_blank">slony.info</a><br>
<mailto:<a href="mailto:Slony1-general@lists.slony.info" target="_blank">Slony1-general@lists.<u></u>slony.info</a>>><br>
<a href="http://lists.slony.info/____mailman/listinfo/slony1-____general" target="_blank">http://lists.slony.info/____<u></u>mailman/listinfo/slony1-____<u></u>general</a><br>
<<a href="http://lists.slony.info/__mailman/listinfo/slony1-__general" target="_blank">http://lists.slony.info/__<u></u>mailman/listinfo/slony1-__<u></u>general</a>><div class="im"><br>
<br>
<br>
<<a href="http://lists.slony.info/__mailman/listinfo/slony1-__general" target="_blank">http://lists.slony.info/__<u></u>mailman/listinfo/slony1-__<u></u>general</a><br>
<<a href="http://lists.slony.info/mailman/listinfo/slony1-general" target="_blank">http://lists.slony.info/<u></u>mailman/listinfo/slony1-<u></u>general</a>>><br>
<br>
<br>
<br>
<br>
<br>
--<br>
Sandeep Thakkar<br>
<br>
<br>
<br>
<br>
<br>
--<br>
Sandeep Thakkar<br>
<br>
</div></blockquote>
<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Sandeep Thakkar<div><br></div></div>
</div></div></div>