Re: BDR conpilation error un Ubuntu 12.4 LTS - Mailing list pgsql-general

Hi Stefano,

I used the same version of gcc (Ubuntu/Linaro 4.6.3-1ubuntu5), and I followed your steps compiling without problems. I also considered the same git branch (bdr/0.7.1) as in your case. Taking a look to the error you obtained it sounds like an error due to the code, regardless of the used version of gcc. I would suggest to:

* be sure you have properly installed the dependencies (build-essential libreadline-dev zlib1g-dev libssl-dev bison flex)

* try to compile the code in the bdr-REL9_4_STABLE git branch

Anyway, I followed the same procedure you reported in your first email and it works.

Giuseppe.

2014-12-23 8:45 GMT+01:00 stefano bonnin <stefano.bonnin@gmail.com>:

I have upgraded GCC to: 

gcc (Ubuntu 4.8.1-2ubuntu1~12.04) 4.8.1

Now the error is: 

make -C ../../src/interfaces/libpq all

make[1]: Entering directory `/usr/src/meteosmit/postgresql-BDR/2ndquadrant_bdr/src/interfaces/libpq'

make[1]: Nothing to be done for `all'.

make[1]: Leaving directory `/usr/src/meteosmit/postgresql-BDR/2ndquadrant_bdr/src/interfaces/libpq'

sed '0,/BDR_VERSION_DATE/s,\(BDR_VERSION_DATE\).*,\1 "2014-12-23",;0,/BDR_VERSION_GITHASH/s,\(BDR_VERSION_GITHASH\).*,\1 "a63674e",' bdr_version.h.in >bdr_version.h

gcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute -Wformat-security -fno-strict-aliasing -fwrapv -fexcess-precision=standard -fpic -I../../src/interfaces/libpq -I. -I. -I../../src/include -D_GNU_SOURCE   -c -o bdr.o bdr.c

bdr.c: In function ‘bdr_perdb_worker_main’:

bdr.c:1057:10: warning: ‘rc’ may be used uninitialized in this function [-Wmaybe-uninitialized]

   if (rc & WL_POSTMASTER_DEATH)

          ^

gcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute -Wformat-security -fno-strict-aliasing -fwrapv -fexcess-precision=standard -fpic -I../../src/interfaces/libpq -I. -I. -I../../src/include -D_GNU_SOURCE   -c -o bdr_apply.o bdr_apply.c

In file included from ../../src/include/postgres.h:48:0,

                 from bdr_apply.c:15:

bdr_apply.c: In function ‘process_remote_commit’:

bdr_apply.c:288:22: error: invalid operands to binary >> (have ‘TimestampTz’ and ‘int’)

    (uint32) (end_lsn >> 32), (uint32) end_lsn,

                      ^

../../src/include/utils/elog.h:254:23: note: in definition of macro ‘elog’

   elog_finish(elevel, __VA_ARGS__); \

                       ^

bdr_apply.c:358:22: error: invalid operands to binary >> (have ‘TimestampTz’ and ‘int’)

      (uint32)(end_lsn>>32), (uint32)end_lsn,

                      ^

../../src/include/utils/elog.h:117:14: note: in definition of macro ‘ereport_domain’

    errfinish rest; \

              ^

bdr_apply.c:355:3: note: in expansion of macro ‘ereport’

   ereport(LOG,

   ^

make: *** [bdr_apply.o] Error 1

Regards.

2014-12-23 8:11 GMT+01:00 stefano bonnin <stefano.bonnin@gmail.com>:

Hi Giuseppe, 

gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3

a newer version needed?

2014-12-22 14:00 GMT+01:00 Giuseppe Broccolo <giuseppe.broccolo@2ndquadrant.it>:

Hi Stefano,

Which version of gcc are you using?

Giuseppe.

2014-12-22 9:52 GMT+01:00 stefano bonnin <stefano.bonnin@gmail.com>:

Hi all, I have followed the wiki about postgresql BDR: 

OS: Ubuntu 12.04.5 LTS

• git clone git://git.postgresql.org/git/2ndquadrant_bdr.git
• cd 2ndquadrant_bdr
• git checkout bdr/0.7.1
• ./configure --prefix=$HOME/bdr --with-openssl
• make
• make install

To install the BDR extension you'd then run:

• (cd contrib/btree_gist && make && make install)
• (cd contrib/bdr && make && make install)

or to instead install all contribs (useful to include widely used extensions like hstore):

• (cd contrib && make all)
• (cd contrib && make install)

BUT during cd contrib/bdr && make I obtain the following error:

make -C ../../src/interfaces/libpq all

make[1]: Entering directory `/usr/src/meteosmit/postgresql-BDR/2ndquadrant_bdr/src/interfaces/libpq'

make[1]: Nothing to be done for `all'.

make[1]: Leaving directory `/usr/src/meteosmit/postgresql-BDR/2ndquadrant_bdr/src/interfaces/libpq'

sed '0,/BDR_VERSION_DATE/s,\(BDR_VERSION_DATE\).*,\1 "2014-12-22",;0,/BDR_VERSION_GITHASH/s,\(BDR_VERSION_GITHASH\).*,\1 "a63674e",' bdr_version.h.in >bdr_version.h

gcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute -Wformat-security -fno-strict-aliasing -fwrapv -fexcess-precision=standard -fpic -I../../src/interfaces/libpq -I. -I. -I../../src/include -D_GNU_SOURCE   -c -o bdr.o bdr.c

bdr.c: In function ‘bdr_perdb_worker_main’:

bdr.c:1057:10: warning: ‘rc’ may be used uninitialized in this function [-Wuninitialized]

gcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute -Wformat-security -fno-strict-aliasing -fwrapv -fexcess-precision=standard -fpic -I../../src/interfaces/libpq -I. -I. -I../../src/include -D_GNU_SOURCE   -c -o bdr_apply.o bdr_apply.c

bdr_apply.c: In function ‘process_remote_commit’:

bdr_apply.c:286:2: error: invalid operands to binary >> (have ‘TimestampTz’ and ‘int’)

bdr_apply.c:355:3: error: invalid operands to binary >> (have ‘TimestampTz’ and ‘int’)

make: *** [bdr_apply.o] Error 1

Any help appreciated. Thanks.

--

Giuseppe Broccolo - 2ndQuadrant Italy
PostgreSQL Training, Services and Support
giuseppe.broccolo@2ndQuadrant.it | www.2ndQuadrant.it

--

Stefano Bonnin

email: stefano.bonnin@gmail.com

Informativa Art. 13 D.Lgs N° 196 del 30/06/2003 
Qualora questa e-mail risulti inviata ad un destinatario errato, Vi invitiamo a distruggerla immediatamente. Ai sensi del D.Lgs 30/06/03 n. 196 (c.d. Testo Unico sulla Privacy) e seguenti regolamenti, si dovrà dare comunicazione dell'errata ricezione all' indirizzo e-mail del mittente, nonchè provvedere alla distruzione del documento erroneamente ricevuto. Il mittente non è responsabile per dati comunicati e conosciuti contravvenendo a questo invito. Il presente documento ha carattere informale, non impegna la Società e non costituisce corrispondenza ufficiale della stessa.Il suo contenuto, per avere valore ai fini contrattuali, dovrà essere oggetto di corrispondenza regolarmente firmata, da inoltrare secondo i canoni tradizionali

This e-mail is confidential and may also contain privileged information. If you are not the intended recipient you are not authorised to read, print, save, process or disclose this message. If you have received this message by mistake, please inform the sender immediately and delete this e-mail, its attachments and any copies. Any use, distribution, reproduction or disclosure by any person other than the intended recipient is strictly prohibited and the person responsible may incur penalties.

--

Stefano Bonnin

email: stefano.bonnin@gmail.com

Informativa Art. 13 D.Lgs N° 196 del 30/06/2003 
Qualora questa e-mail risulti inviata ad un destinatario errato, Vi invitiamo a distruggerla immediatamente. Ai sensi del D.Lgs 30/06/03 n. 196 (c.d. Testo Unico sulla Privacy) e seguenti regolamenti, si dovrà dare comunicazione dell'errata ricezione all' indirizzo e-mail del mittente, nonchè provvedere alla distruzione del documento erroneamente ricevuto. Il mittente non è responsabile per dati comunicati e conosciuti contravvenendo a questo invito. Il presente documento ha carattere informale, non impegna la Società e non costituisce corrispondenza ufficiale della stessa.Il suo contenuto, per avere valore ai fini contrattuali, dovrà essere oggetto di corrispondenza regolarmente firmata, da inoltrare secondo i canoni tradizionali

This e-mail is confidential and may also contain privileged information. If you are not the intended recipient you are not authorised to read, print, save, process or disclose this message. If you have received this message by mistake, please inform the sender immediately and delete this e-mail, its attachments and any copies. Any use, distribution, reproduction or disclosure by any person other than the intended recipient is strictly prohibited and the person responsible may incur penalties.

--

Giuseppe Broccolo - 2ndQuadrant Italy
PostgreSQL Training, Services and Support
giuseppe.broccolo@2ndQuadrant.it | www.2ndQuadrant.it