From: DIMI <nic...@un...> - 2013-10-30 09:14:16
|
Thanks, the patch can now be applied. But, it doesn’t fix the problem: I still get the same build errors. Nicola On 30/ott/2013, at 09:58, Koichi Suzuki <koi...@gm...> wrote: > Because the patch is for vanilla PG. Sometimes we have patch conflict. Here's a hack of the patch. Because the nature of the patch does not have any bad influence, I hope you can try this. Please let me know how it works. > > # Please understand that this is really a quick hack and I'm not tracking this patch in a good manner. > > Good Luck; > > --- > Koichi Suzuki > > > 2013/10/30 DIMI <nic...@un...> > On 30/ott/2013, at 08:51, Michael Paquier <mic...@gm...> wrote: > > > There have been fixes these days in Postgres core for Mavericks for strlcpy: > > http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=a1f86e70c8d9a152eaa50cc17e5249da10d3e758ì > > I cannot apply that patch to Postgres-XC 1.1. And after making the change manually, I still get the same build errors. Am I missing something? > > Nicola > > > <tupdesc.c.patch> |