Menu
▾
▴
postgres-xc-bugs
|
From: DIMI <nic...@un...> - 2013-10-29 13:35:29
|
Name: Nicola Vitacolonna
Email: nvi...@gm...
System Configuration:
---------------------
Architecture : Intel Pentium
Operating System : OS X 10.9 (Mavericks)
Postgres-XC version : Postgres-XC 1.1
Compiler used : gcc —version
Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn)
Target: x86_64-apple-darwin13.0.0
Thread model: posix
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1
Please enter a FULL description of your problem:
------------------------------------------------
./configure & make fails with the following errors, possibly related with the fact that clang links against libc++ instead of libstdc++:
[…]
cc -DPGXC -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute -Wformat-security -fno-strict-aliasing -fwrapv -I../../../src/include -c -o strlcpy.o strlcpy.c
strlcpy.c:46:1: error: expected parameter declarator
strlcpy(char *dst, const char *src, size_t siz)
^
/usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'
__builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
^
/usr/include/secure/_common.h:39:62: note: expanded from macro '__darwin_obsz'
#define __darwin_obsz(object) __builtin_object_size (object, _USE_FORTIFY_LEVEL > 1 ? 1 : 0)
^
/usr/include/secure/_common.h:30:32: note: expanded from macro '_USE_FORTIFY_LEVEL'
# define _USE_FORTIFY_LEVEL 2
^
strlcpy.c:46:1: error: expected ')'
/usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'
__builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
^
/usr/include/secure/_common.h:39:62: note: expanded from macro '__darwin_obsz'
#define __darwin_obsz(object) __builtin_object_size (object, _USE_FORTIFY_LEVEL > 1 ? 1 : 0)
^
/usr/include/secure/_common.h:30:32: note: expanded from macro '_USE_FORTIFY_LEVEL'
# define _USE_FORTIFY_LEVEL 2
^
strlcpy.c:46:1: note: to match this '('
/usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'
__builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
^
/usr/include/secure/_common.h:39:53: note: expanded from macro '__darwin_obsz'
#define __darwin_obsz(object) __builtin_object_size (object, _USE_FORTIFY_LEVEL > 1 ? 1 : 0)
^
strlcpy.c:46:1: warning: type specifier missing, defaults to 'int' [-Wimplicit-int]
strlcpy(char *dst, const char *src, size_t siz)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'
__builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
^~~~~~~~~~~~~~~~~~~~
/usr/include/secure/_common.h:39:31: note: expanded from macro '__darwin_obsz'
#define __darwin_obsz(object) __builtin_object_size (object, _USE_FORTIFY_LEVEL > 1 ? 1 : 0)
^~~~~~~~~~~~~~~~~~~~~
strlcpy.c:46:1: error: conflicting types for '__builtin___strlcpy_chk'
/usr/include/secure/_string.h:105:3: note: expanded from macro 'strlcpy'
__builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
^
strlcpy.c:46:1: note: '__builtin___strlcpy_chk' is a builtin with type 'unsigned long (char *, const char *, unsigned long, unsigned long)'
/usr/include/secure/_string.h:105:3: note: expanded from macro 'strlcpy'
__builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
^
strlcpy.c:46:1: error: definition of builtin function '__builtin___strlcpy_chk'
strlcpy(char *dst, const char *src, size_t siz)
^
/usr/include/secure/_string.h:105:3: note: expanded from macro 'strlcpy'
__builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
^
1 warning and 4 errors generated.
make[3]: *** [strlcpy.o] Error 1
make[2]: *** [all-libpq-recurse] Error 2
make[1]: *** [all-gtm-recurse] Error 2
make: *** [all-src-recurse] Error 2
Please describe a way to repeat the problem. Please try to provide a
concise reproducible example, if at all possible:
----------------------------------------------------------------------
Just ./configure & make.
|
|
From: Koichi S. <koi...@gm...> - 2013-10-30 01:45:10
|
I tried ./configure at Mountain Lion without any problems. Build was
successful too. Maybe this is Marverick-specific.
Postgres-XC imports most of ./configure from PostgreSQL. Could you try
./configure for PostgreSQL and see if you have similar problems? If you
are successful, maybe we can update our ./configure based on the latest PG
resource. Sorry I cannot find a time to upgrade my Macs into Marvericks
for this couple of days at least.
Best regards;
---
Koichi Suzuki
2013/10/29 DIMI <nic...@un...>
> Name: Nicola Vitacolonna
> Email: nvi...@gm...
>
> System Configuration:
> ---------------------
> Architecture : Intel Pentium
> Operating System : OS X 10.9 (Mavericks)
> Postgres-XC version : Postgres-XC 1.1
> Compiler used : gcc —version
>
> Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn)
> Target: x86_64-apple-darwin13.0.0
> Thread model: posix
> Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr
> --with-gxx-include-dir=/usr/include/c++/4.2.1
>
>
> Please enter a FULL description of your problem:
> ------------------------------------------------
> ./configure & make fails with the following errors, possibly related with
> the fact that clang links against libc++ instead of libstdc++:
>
> […]
> cc -DPGXC -O2 -Wall -Wmissing-prototypes -Wpointer-arith
> -Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute
> -Wformat-security -fno-strict-aliasing -fwrapv -I../../../src/include -c
> -o strlcpy.o strlcpy.c
> strlcpy.c:46:1: error: expected parameter declarator
> strlcpy(char *dst, const char *src, size_t siz)
> ^
> /usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'
> __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
> ^
> /usr/include/secure/_common.h:39:62: note: expanded from macro
> '__darwin_obsz'
> #define __darwin_obsz(object) __builtin_object_size (object,
> _USE_FORTIFY_LEVEL > 1 ? 1 : 0)
> ^
> /usr/include/secure/_common.h:30:32: note: expanded from macro
> '_USE_FORTIFY_LEVEL'
> # define _USE_FORTIFY_LEVEL 2
> ^
> strlcpy.c:46:1: error: expected ')'
> /usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'
> __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
> ^
> /usr/include/secure/_common.h:39:62: note: expanded from macro
> '__darwin_obsz'
> #define __darwin_obsz(object) __builtin_object_size (object,
> _USE_FORTIFY_LEVEL > 1 ? 1 : 0)
> ^
> /usr/include/secure/_common.h:30:32: note: expanded from macro
> '_USE_FORTIFY_LEVEL'
> # define _USE_FORTIFY_LEVEL 2
> ^
> strlcpy.c:46:1: note: to match this '('
> /usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'
> __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
> ^
> /usr/include/secure/_common.h:39:53: note: expanded from macro
> '__darwin_obsz'
> #define __darwin_obsz(object) __builtin_object_size (object,
> _USE_FORTIFY_LEVEL > 1 ? 1 : 0)
> ^
> strlcpy.c:46:1: warning: type specifier missing, defaults to 'int'
> [-Wimplicit-int]
> strlcpy(char *dst, const char *src, size_t siz)
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> /usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'
> __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
> ^~~~~~~~~~~~~~~~~~~~
> /usr/include/secure/_common.h:39:31: note: expanded from macro
> '__darwin_obsz'
> #define __darwin_obsz(object) __builtin_object_size (object,
> _USE_FORTIFY_LEVEL > 1 ? 1 : 0)
> ^~~~~~~~~~~~~~~~~~~~~
> strlcpy.c:46:1: error: conflicting types for '__builtin___strlcpy_chk'
> /usr/include/secure/_string.h:105:3: note: expanded from macro 'strlcpy'
> __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
> ^
> strlcpy.c:46:1: note: '__builtin___strlcpy_chk' is a builtin with type
> 'unsigned long (char *, const char *, unsigned long, unsigned long)'
> /usr/include/secure/_string.h:105:3: note: expanded from macro 'strlcpy'
> __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
> ^
> strlcpy.c:46:1: error: definition of builtin function
> '__builtin___strlcpy_chk'
> strlcpy(char *dst, const char *src, size_t siz)
> ^
> /usr/include/secure/_string.h:105:3: note: expanded from macro 'strlcpy'
> __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
> ^
> 1 warning and 4 errors generated.
> make[3]: *** [strlcpy.o] Error 1
> make[2]: *** [all-libpq-recurse] Error 2
> make[1]: *** [all-gtm-recurse] Error 2
> make: *** [all-src-recurse] Error 2
>
>
> Please describe a way to repeat the problem. Please try to provide a
> concise reproducible example, if at all possible:
> ----------------------------------------------------------------------
> Just ./configure & make.
>
>
>
> ------------------------------------------------------------------------------
> Android is increasing in popularity, but the open development platform that
> developers love is also attractive to malware creators. Download this white
> paper to learn more about secure code signing practices that can help keep
> Android apps secure.
> http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
> _______________________________________________
> Postgres-xc-bugs mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-bugs
>
|
|
From: DIMI <nic...@un...> - 2013-10-30 06:31:50
|
PostgreSQL 9.3.1 builds just fine. I, too, believe that it is Maverick-specific, since I had no problems with building Postgres-XC on previous systems.
Nicola
On 30/ott/2013, at 02:45, Koichi Suzuki <koi...@gm...> wrote:
> I tried ./configure at Mountain Lion without any problems. Build was successful too. Maybe this is Marverick-specific.
>
> Postgres-XC imports most of ./configure from PostgreSQL. Could you try ./configure for PostgreSQL and see if you have similar problems? If you are successful, maybe we can update our ./configure based on the latest PG resource. Sorry I cannot find a time to upgrade my Macs into Marvericks for this couple of days at least.
>
> Best regards;
>
> ---
> Koichi Suzuki
>
>
> 2013/10/29 DIMI <nic...@un...>
> Name: Nicola Vitacolonna
> Email: nvi...@gm...
>
> System Configuration:
> ---------------------
> Architecture : Intel Pentium
> Operating System : OS X 10.9 (Mavericks)
> Postgres-XC version : Postgres-XC 1.1
> Compiler used : gcc —version
>
> Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn)
> Target: x86_64-apple-darwin13.0.0
> Thread model: posix
> Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1
>
>
> Please enter a FULL description of your problem:
> ------------------------------------------------
> ./configure & make fails with the following errors, possibly related with the fact that clang links against libc++ instead of libstdc++:
>
> […]
> cc -DPGXC -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute -Wformat-security -fno-strict-aliasing -fwrapv -I../../../src/include -c -o strlcpy.o strlcpy.c
> strlcpy.c:46:1: error: expected parameter declarator
> strlcpy(char *dst, const char *src, size_t siz)
> ^
> /usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'
> __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
> ^
> /usr/include/secure/_common.h:39:62: note: expanded from macro '__darwin_obsz'
> #define __darwin_obsz(object) __builtin_object_size (object, _USE_FORTIFY_LEVEL > 1 ? 1 : 0)
> ^
> /usr/include/secure/_common.h:30:32: note: expanded from macro '_USE_FORTIFY_LEVEL'
> # define _USE_FORTIFY_LEVEL 2
> ^
> strlcpy.c:46:1: error: expected ')'
> /usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'
> __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
> ^
> /usr/include/secure/_common.h:39:62: note: expanded from macro '__darwin_obsz'
> #define __darwin_obsz(object) __builtin_object_size (object, _USE_FORTIFY_LEVEL > 1 ? 1 : 0)
> ^
> /usr/include/secure/_common.h:30:32: note: expanded from macro '_USE_FORTIFY_LEVEL'
> # define _USE_FORTIFY_LEVEL 2
> ^
> strlcpy.c:46:1: note: to match this '('
> /usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'
> __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
> ^
> /usr/include/secure/_common.h:39:53: note: expanded from macro '__darwin_obsz'
> #define __darwin_obsz(object) __builtin_object_size (object, _USE_FORTIFY_LEVEL > 1 ? 1 : 0)
> ^
> strlcpy.c:46:1: warning: type specifier missing, defaults to 'int' [-Wimplicit-int]
> strlcpy(char *dst, const char *src, size_t siz)
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> /usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'
> __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
> ^~~~~~~~~~~~~~~~~~~~
> /usr/include/secure/_common.h:39:31: note: expanded from macro '__darwin_obsz'
> #define __darwin_obsz(object) __builtin_object_size (object, _USE_FORTIFY_LEVEL > 1 ? 1 : 0)
> ^~~~~~~~~~~~~~~~~~~~~
> strlcpy.c:46:1: error: conflicting types for '__builtin___strlcpy_chk'
> /usr/include/secure/_string.h:105:3: note: expanded from macro 'strlcpy'
> __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
> ^
> strlcpy.c:46:1: note: '__builtin___strlcpy_chk' is a builtin with type 'unsigned long (char *, const char *, unsigned long, unsigned long)'
> /usr/include/secure/_string.h:105:3: note: expanded from macro 'strlcpy'
> __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
> ^
> strlcpy.c:46:1: error: definition of builtin function '__builtin___strlcpy_chk'
> strlcpy(char *dst, const char *src, size_t siz)
> ^
> /usr/include/secure/_string.h:105:3: note: expanded from macro 'strlcpy'
> __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
> ^
> 1 warning and 4 errors generated.
> make[3]: *** [strlcpy.o] Error 1
> make[2]: *** [all-libpq-recurse] Error 2
> make[1]: *** [all-gtm-recurse] Error 2
> make: *** [all-src-recurse] Error 2
>
>
> Please describe a way to repeat the problem. Please try to provide a
> concise reproducible example, if at all possible:
> ----------------------------------------------------------------------
> Just ./configure & make.
>
>
> ------------------------------------------------------------------------------
> Android is increasing in popularity, but the open development platform that
> developers love is also attractive to malware creators. Download this white
> paper to learn more about secure code signing practices that can help keep
> Android apps secure.
> http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
> _______________________________________________
> Postgres-xc-bugs mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-bugs
>
|
|
From: Koichi S. <koi...@gm...> - 2013-10-30 07:04:52
|
I see. We're merging PostgreSQL9.3.1 code into XC. Hope this helps
building XC with Marverics. Merge with PostgreSQL 9.3 will be available
as XC release 1.2, hopefully at the end of the year.
Regards;
---
Koichi Suzuki
2013/10/30 DIMI <nic...@un...>
> PostgreSQL 9.3.1 builds just fine. I, too, believe that it is
> Maverick-specific, since I had no problems with building Postgres-XC on
> previous systems.
>
> Nicola
>
> On 30/ott/2013, at 02:45, Koichi Suzuki <koi...@gm...> wrote:
>
> I tried ./configure at Mountain Lion without any problems. Build was
> successful too. Maybe this is Marverick-specific.
>
> Postgres-XC imports most of ./configure from PostgreSQL. Could you try
> ./configure for PostgreSQL and see if you have similar problems? If you
> are successful, maybe we can update our ./configure based on the latest PG
> resource. Sorry I cannot find a time to upgrade my Macs into Marvericks
> for this couple of days at least.
>
> Best regards;
>
> ---
> Koichi Suzuki
>
>
> 2013/10/29 DIMI <nic...@un...>
>
>> Name: Nicola Vitacolonna
>> Email: nvi...@gm...
>>
>> System Configuration:
>> ---------------------
>> Architecture : Intel Pentium
>> Operating System : OS X 10.9 (Mavericks)
>> Postgres-XC version : Postgres-XC 1.1
>> Compiler used : gcc —version
>>
>> Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn)
>> Target: x86_64-apple-darwin13.0.0
>> Thread model: posix
>> Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr
>> --with-gxx-include-dir=/usr/include/c++/4.2.1
>>
>>
>> Please enter a FULL description of your problem:
>> ------------------------------------------------
>> ./configure & make fails with the following errors, possibly related
>> with the fact that clang links against libc++ instead of libstdc++:
>>
>> […]
>> cc -DPGXC -O2 -Wall -Wmissing-prototypes -Wpointer-arith
>> -Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute
>> -Wformat-security -fno-strict-aliasing -fwrapv -I../../../src/include -c
>> -o strlcpy.o strlcpy.c
>> strlcpy.c:46:1: error: expected parameter declarator
>> strlcpy(char *dst, const char *src, size_t siz)
>> ^
>> /usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'
>> __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
>> ^
>> /usr/include/secure/_common.h:39:62: note: expanded from macro
>> '__darwin_obsz'
>> #define __darwin_obsz(object) __builtin_object_size (object,
>> _USE_FORTIFY_LEVEL > 1 ? 1 : 0)
>> ^
>> /usr/include/secure/_common.h:30:32: note: expanded from macro
>> '_USE_FORTIFY_LEVEL'
>> # define _USE_FORTIFY_LEVEL 2
>> ^
>> strlcpy.c:46:1: error: expected ')'
>> /usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'
>> __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
>> ^
>> /usr/include/secure/_common.h:39:62: note: expanded from macro
>> '__darwin_obsz'
>> #define __darwin_obsz(object) __builtin_object_size (object,
>> _USE_FORTIFY_LEVEL > 1 ? 1 : 0)
>> ^
>> /usr/include/secure/_common.h:30:32: note: expanded from macro
>> '_USE_FORTIFY_LEVEL'
>> # define _USE_FORTIFY_LEVEL 2
>> ^
>> strlcpy.c:46:1: note: to match this '('
>> /usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'
>> __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
>> ^
>> /usr/include/secure/_common.h:39:53: note: expanded from macro
>> '__darwin_obsz'
>> #define __darwin_obsz(object) __builtin_object_size (object,
>> _USE_FORTIFY_LEVEL > 1 ? 1 : 0)
>> ^
>> strlcpy.c:46:1: warning: type specifier missing, defaults to 'int'
>> [-Wimplicit-int]
>> strlcpy(char *dst, const char *src, size_t siz)
>> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> /usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'
>> __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
>> ^~~~~~~~~~~~~~~~~~~~
>> /usr/include/secure/_common.h:39:31: note: expanded from macro
>> '__darwin_obsz'
>> #define __darwin_obsz(object) __builtin_object_size (object,
>> _USE_FORTIFY_LEVEL > 1 ? 1 : 0)
>> ^~~~~~~~~~~~~~~~~~~~~
>> strlcpy.c:46:1: error: conflicting types for '__builtin___strlcpy_chk'
>> /usr/include/secure/_string.h:105:3: note: expanded from macro 'strlcpy'
>> __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
>> ^
>> strlcpy.c:46:1: note: '__builtin___strlcpy_chk' is a builtin with type
>> 'unsigned long (char *, const char *, unsigned long, unsigned long)'
>> /usr/include/secure/_string.h:105:3: note: expanded from macro 'strlcpy'
>> __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
>> ^
>> strlcpy.c:46:1: error: definition of builtin function
>> '__builtin___strlcpy_chk'
>> strlcpy(char *dst, const char *src, size_t siz)
>> ^
>> /usr/include/secure/_string.h:105:3: note: expanded from macro 'strlcpy'
>> __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
>> ^
>> 1 warning and 4 errors generated.
>> make[3]: *** [strlcpy.o] Error 1
>> make[2]: *** [all-libpq-recurse] Error 2
>> make[1]: *** [all-gtm-recurse] Error 2
>> make: *** [all-src-recurse] Error 2
>>
>>
>> Please describe a way to repeat the problem. Please try to provide a
>> concise reproducible example, if at all possible:
>> ----------------------------------------------------------------------
>> Just ./configure & make.
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Android is increasing in popularity, but the open development platform
>> that
>> developers love is also attractive to malware creators. Download this
>> white
>> paper to learn more about secure code signing practices that can help keep
>> Android apps secure.
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Postgres-xc-bugs mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-bugs
>>
>
>
>
|
|
From: Michael P. <mic...@gm...> - 2013-10-30 07:51:20
|
On Wed, Oct 30, 2013 at 7:04 AM, Koichi Suzuki <koi...@gm...> wrote: > I see. We're merging PostgreSQL9.3.1 code into XC. Hope this helps > building XC with Marverics. Merge with PostgreSQL 9.3 will be available > as XC release 1.2, hopefully at the end of the year. 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 Note that merging 9.3.1 into REL1_2_STABLE will *not* remove the issue as it has been committed after the release of 9.3.1. In the case of the merge of master branch of Postgres with XC master also this will not be included by default, as this should be done based on commit of `git merge-base master REL9_3_STABLE` and the fix on Postgres core has been added afterwards AFAIK. -- Michael |
|
From: DIMI <nic...@un...> - 2013-10-30 08:17:32
|
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 |
|
From: Koichi S. <koi...@gm...> - 2013-10-30 08:05:46
|
MIchael; Thanks for the info. Maybe we should merge with PG REL9_3_STABLE's latest status as possible, or cherry-pick this specific commit. Regards; --- Koichi Suzuki 2013/10/30 Michael Paquier <mic...@gm...> > On Wed, Oct 30, 2013 at 7:04 AM, Koichi Suzuki <koi...@gm...> > wrote: > > I see. We're merging PostgreSQL9.3.1 code into XC. Hope this helps > > building XC with Marverics. Merge with PostgreSQL 9.3 will be > available > > as XC release 1.2, hopefully at the end of the year. > 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 > Note that merging 9.3.1 into REL1_2_STABLE will *not* remove the issue > as it has been committed after the release of 9.3.1. In the case of > the merge of master branch of Postgres with XC master also this will > not be included by default, as this should be done based on commit of > `git merge-base master REL9_3_STABLE` and the fix on Postgres core has > been added afterwards AFAIK. > -- > Michael > |
|
From: Michael P. <mic...@gm...> - 2013-10-30 08:34:58
|
On Wed, Oct 30, 2013 at 8:05 AM, Koichi Suzuki <koi...@gm...> wrote: > Maybe we should merge with PG REL9_3_STABLE's latest status as possible, No. The merge to 9.3 should be done up to the merge base of Postgres' master and REL9_3_STABLE. > or cherry-pick this specific commit. This would be better. -- Michael |
|
From: Koichi S. <koi...@gm...> - 2013-10-30 08:39:57
|
I don't understand quite well about this. Nicola successfully built PG9.3.1 with Marvericks, while you mentioned that the code is not 9.3.1 but in the latest part of REL9_3_STABLE, which is not available with PG 9.3.1. Could you give me some more clarification on this? Regards; --- Koichi Suzuki 2013/10/30 Michael Paquier <mic...@gm...> > On Wed, Oct 30, 2013 at 7:04 AM, Koichi Suzuki <koi...@gm...> > wrote: > > I see. We're merging PostgreSQL9.3.1 code into XC. Hope this helps > > building XC with Marverics. Merge with PostgreSQL 9.3 will be > available > > as XC release 1.2, hopefully at the end of the year. > 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 > Note that merging 9.3.1 into REL1_2_STABLE will *not* remove the issue > as it has been committed after the release of 9.3.1. In the case of > the merge of master branch of Postgres with XC master also this will > not be included by default, as this should be done based on commit of > `git merge-base master REL9_3_STABLE` and the fix on Postgres core has > been added afterwards AFAIK. > -- > Michael > |
|
From: Michael P. <mic...@gm...> - 2013-10-30 08:51:14
|
On Wed, Oct 30, 2013 at 8:39 AM, Koichi Suzuki <koi...@gm...> wrote: > I don't understand quite well about this. Nicola successfully built > PG9.3.1 with Marvericks, while you mentioned that the code is not 9.3.1 but > in the latest part of REL9_3_STABLE, which is not available with PG 9.3.1. > > Could you give me some more clarification on this? Oops, sorry. You are right. 9.3.1 compiles well with clang on Mavericks. So if REL1_2_STABLE of XC is merged up to 9.3.1 or even the latest commit of Postgres' REL9_3_STABLE it might be fine. For master though... I am not sure. There might be as well some issues related to XC code itself. -- Michael |
|
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> |
|
From: Koichi S. <koi...@gm...> - 2013-10-31 02:08:34
|
I'm interested if ./configure is successful. Maybe the patch Michael suggested may not be sufficient. I suspect there's another problem in ./configure. If you allow me some time (maybe some time next week) until I upgrade my Macs to Marberics, I can reproduce the problem. Please understand that XC has not announced OS X support so far because we don't have sufficient resource. It will be nice if you help to support XC on OS X, or any other platforms other than Intel Linux. Regards; --- Koichi Suzuki 2013/10/30 DIMI <nic...@un...> > 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> > > > |
|
From: DIMI <nic...@un...> - 2013-10-31 06:13:50
|
Please find enclosed the output of ./configure. I don’t see anything apparently wrong. I’d be happy to contribute supporting XC on OS X, although I don’t have much familiarity with the code. Should I subscribe to some developer mailing list? Nicola On 31/ott/2013, at 03:08, Koichi Suzuki <koi...@gm...> wrote: > I'm interested if ./configure is successful. > > Maybe the patch Michael suggested may not be sufficient. I suspect there's another problem in ./configure. If you allow me some time (maybe some time next week) until I upgrade my Macs to Marberics, I can reproduce the problem. > > Please understand that XC has not announced OS X support so far because we don't have sufficient resource. It will be nice if you help to support XC on OS X, or any other platforms other than Intel Linux. > > Regards; > > --- > Koichi Suzuki > > > 2013/10/30 DIMI <nic...@un...> > 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> > > |
|
From: Koichi S. <koi...@gm...> - 2013-10-31 07:17:05
|
Thank you for your interest. Yes, you can subscribe developers and general mailing list to watch watch is going on. Regards; --- Koichi Suzuki 2013/10/31 DIMI <nic...@un...> > Please find enclosed the output of ./configure. I don’t see anything > apparently wrong. > > I’d be happy to contribute supporting XC on OS X, although I don’t have > much familiarity with the code. Should I subscribe to some developer > mailing list? > > Nicola > > > > > On 31/ott/2013, at 03:08, Koichi Suzuki <koi...@gm...> wrote: > > I'm interested if ./configure is successful. > > Maybe the patch Michael suggested may not be sufficient. I suspect > there's another problem in ./configure. If you allow me some time (maybe > some time next week) until I upgrade my Macs to Marberics, I can reproduce > the problem. > > Please understand that XC has not announced OS X support so far because we > don't have sufficient resource. It will be nice if you help to support XC > on OS X, or any other platforms other than Intel Linux. > > Regards; > > --- > Koichi Suzuki > > > 2013/10/30 DIMI <nic...@un...> > >> 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> >> >> >> > > > |
|
From: Nikhil S. <ni...@st...> - 2013-10-31 11:18:49
|
Hi Nicola, Suzuki-san, IMO, no patch is needed for XC compilation on latest OS X. Please append this to the CFLAGS: "-D_FORTIFY_SOURCE=0" and it should compile ok on Maverick. ./configure CFLAGS="-D_FORTIFY_SOURCE=0" Did work for me. Regards, Nikhils On Thu, Oct 31, 2013 at 11:42 AM, DIMI <nic...@un...> wrote: > Please find enclosed the output of ./configure. I don’t see anything > apparently wrong. > > I’d be happy to contribute supporting XC on OS X, although I don’t have > much familiarity with the code. Should I subscribe to some developer > mailing list? > > Nicola > > > > > On 31/ott/2013, at 03:08, Koichi Suzuki <koi...@gm...> wrote: > > I'm interested if ./configure is successful. > > Maybe the patch Michael suggested may not be sufficient. I suspect > there's another problem in ./configure. If you allow me some time (maybe > some time next week) until I upgrade my Macs to Marberics, I can reproduce > the problem. > > Please understand that XC has not announced OS X support so far because we > don't have sufficient resource. It will be nice if you help to support XC > on OS X, or any other platforms other than Intel Linux. > > Regards; > > --- > Koichi Suzuki > > > 2013/10/30 DIMI <nic...@un...> > >> 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> >> >> >> > > > > ------------------------------------------------------------------------------ > Android is increasing in popularity, but the open development platform that > developers love is also attractive to malware creators. Download this white > paper to learn more about secure code signing practices that can help keep > Android apps secure. > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-bugs mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-bugs > > -- StormDB - http://www.stormdb.com The Database Cloud |
|
From: Koichi S. <koi...@gm...> - 2013-10-31 15:30:42
|
Thanks Nikhil. We may need a way to set it up automatically via ./configure. Nicola, could you test this? This CFLAGS setting may disable -O2 optimization so it would be better to add this. Regards; --- Koichi Suzuki 2013/10/31 Nikhil Sontakke <ni...@st...> > Hi Nicola, Suzuki-san, > > IMO, no patch is needed for XC compilation on latest OS X. > > Please append this to the CFLAGS: "-D_FORTIFY_SOURCE=0" and it should > compile ok on Maverick. > > ./configure CFLAGS="-D_FORTIFY_SOURCE=0" > > Did work for me. > > Regards, > Nikhils > > > > On Thu, Oct 31, 2013 at 11:42 AM, DIMI <nic...@un...>wrote: > >> Please find enclosed the output of ./configure. I don’t see anything >> apparently wrong. >> >> I’d be happy to contribute supporting XC on OS X, although I don’t have >> much familiarity with the code. Should I subscribe to some developer >> mailing list? >> >> Nicola >> >> >> >> >> On 31/ott/2013, at 03:08, Koichi Suzuki <koi...@gm...> wrote: >> >> I'm interested if ./configure is successful. >> >> Maybe the patch Michael suggested may not be sufficient. I suspect >> there's another problem in ./configure. If you allow me some time (maybe >> some time next week) until I upgrade my Macs to Marberics, I can reproduce >> the problem. >> >> Please understand that XC has not announced OS X support so far because >> we don't have sufficient resource. It will be nice if you help to support >> XC on OS X, or any other platforms other than Intel Linux. >> >> Regards; >> >> --- >> Koichi Suzuki >> >> >> 2013/10/30 DIMI <nic...@un...> >> >>> 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> >>> >>> >>> >> >> >> >> ------------------------------------------------------------------------------ >> Android is increasing in popularity, but the open development platform >> that >> developers love is also attractive to malware creators. Download this >> white >> paper to learn more about secure code signing practices that can help keep >> Android apps secure. >> >> http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk >> _______________________________________________ >> Postgres-xc-bugs mailing list >> Pos...@li... >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-bugs >> >> > > > -- > StormDB - http://www.stormdb.com > The Database Cloud > |
|
From: DIMI <nic...@un...> - 2013-10-31 19:14:50
|
I confirm that Nikhil’s suggestion works without patching! Nicola On 31/ott/2013, at 16:30, Koichi Suzuki <koi...@gm...> wrote: > Thanks Nikhil. We may need a way to set it up automatically via ./configure. > > Nicola, could you test this? This CFLAGS setting may disable -O2 optimization so it would be better to add this. > > Regards; > > --- > Koichi Suzuki > > > 2013/10/31 Nikhil Sontakke <ni...@st...> > Hi Nicola, Suzuki-san, > > IMO, no patch is needed for XC compilation on latest OS X. > > Please append this to the CFLAGS: "-D_FORTIFY_SOURCE=0" and it should compile ok on Maverick. > > ./configure CFLAGS="-D_FORTIFY_SOURCE=0" > > Did work for me. > > Regards, > Nikhils > > > > On Thu, Oct 31, 2013 at 11:42 AM, DIMI <nic...@un...> wrote: > Please find enclosed the output of ./configure. I don’t see anything apparently wrong. > > I’d be happy to contribute supporting XC on OS X, although I don’t have much familiarity with the code. Should I subscribe to some developer mailing list? > > Nicola > > > > > On 31/ott/2013, at 03:08, Koichi Suzuki <koi...@gm...> wrote: > >> I'm interested if ./configure is successful. >> >> Maybe the patch Michael suggested may not be sufficient. I suspect there's another problem in ./configure. If you allow me some time (maybe some time next week) until I upgrade my Macs to Marberics, I can reproduce the problem. >> >> Please understand that XC has not announced OS X support so far because we don't have sufficient resource. It will be nice if you help to support XC on OS X, or any other platforms other than Intel Linux. >> >> Regards; >> >> --- >> Koichi Suzuki >> >> >> 2013/10/30 DIMI <nic...@un...> >> 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> >> >> > > > ------------------------------------------------------------------------------ > Android is increasing in popularity, but the open development platform that > developers love is also attractive to malware creators. Download this white > paper to learn more about secure code signing practices that can help keep > Android apps secure. > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-bugs mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-bugs > > > > > -- > StormDB - http://www.stormdb.com > The Database Cloud > |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X