Menu
▾
▴
Re: [Postgres-xc-bugs] Postgres-xc 1.1 does not build with clang and libc++
|
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
>>
>
>
>
|
