Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cCHb9-000209-MW for pgsql-pkg-yum@arkaria.postgresql.org; Thu, 01 Dec 2016 02:59:47 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cCHb8-0005Nw-TH for pgsql-pkg-yum@arkaria.postgresql.org; Thu, 01 Dec 2016 02:59:46 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cCHb8-0005Nq-Cl for pgsql-pkg-yum@postgresql.org; Thu, 01 Dec 2016 02:59:46 +0000 Received: from mail-io0-x22a.google.com ([2607:f8b0:4001:c06::22a]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1cCHb3-0000Q8-La for pgsql-pkg-yum@postgresql.org; Thu, 01 Dec 2016 02:59:45 +0000 Received: by mail-io0-x22a.google.com with SMTP id j65so391764384iof.0 for ; Wed, 30 Nov 2016 18:59:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=georepublic-de.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=KwuGtPDZkqEneKREjHA7m6scNs6DgZvcVx6yrhAsFFE=; b=ARG50MwTarc/5yZjPg9q6xDzBtbnK3zBYuPz8BHI13cdF0RWJYP5KiguMG8Q67uYxG e8AHtx+HkFuMztspYm+OKUntJ32nr+rHzdw6Q5hCGPUyPPvrkKX8iVGgo1Rm4pU+EnBV 4LBZ5u4dWxXifzbA+yTisymxpkBw8gW6gMz12+gFLYJt4hSLQZVnWt4AOJDbUID8jzJO IpQP/aPM0R0qbqK3YKF7DzepFbBk5p5/zOPIiZm3wcgii637DMgiMtDS2yIXuYY9pj5t fFJ64pE0nqzVNJP47DH3r2Tda0k725KuYQM66dwEWPQiif5Jlf5Nz/4Wkb7/uvkJbeWC nI+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=KwuGtPDZkqEneKREjHA7m6scNs6DgZvcVx6yrhAsFFE=; b=TGCE3fcLJOpfs84LOVffaQ3pG3FkvK+bRbPc/0dt8eph8r4/+ZkPs3ReI2BbI4rePH 5RSE6Zts0gpsFPRWc8Ngv7moRtwKuDELwhHm/bjorJDt9luMCM7FeXFlq1pGftRa458C CtmW0KLxmh3n2xofc8p0AAzW3FAxN8KIWG1Pz/ONg1JuBRbFdP/m74u+k0cTA3JC0zeZ pmST31trHJQDrEBq0b6HZW/Kb4870X1k5Nh1YCoorD+ihqtzvdV9imPWgBQ3mCLgnwdp vWdjK96gq+IqWRrFXX5CKbvA05JBSrCTyt5moNSmBuTQx+p8L8wuXVUrE6TT1GfwOdBO Jr7g== X-Gm-Message-State: AKaTC00Nv+ziraLKnwTV1Wr2xTOYLixBdi9fztlzI8ZZPbBc9oXbszfh0gx+nkOuR2gWTONJabox6YZV4Q7qZA== X-Received: by 10.107.32.141 with SMTP id g135mr23637710iog.96.1480561180464; Wed, 30 Nov 2016 18:59:40 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.144.17 with HTTP; Wed, 30 Nov 2016 18:59:39 -0800 (PST) In-Reply-To: References: <1475057321.24885.26.camel@gunduz.org> <1475220454.24885.131.camel@gunduz.org> <1475240709.24885.136.camel@gunduz.org> <20160930141232.h65dcwoeybbuye2l@msg.df7cb.de> <1475417694.27753.7.camel@gunduz.org> From: Vicky Vergara Date: Wed, 30 Nov 2016 20:59:39 -0600 Message-ID: Subject: Re: PostGIS 2.3 and PgRouting 2.0.3? To: Scott Mugnaini Cc: =?UTF-8?B?RGV2cmltIEfDvG5kw7x6?= , Christoph Berg , pgsql-pkg-yum Content-Type: multipart/alternative; boundary=001a1141c3723b0b22054290039b X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-pkg-yum Precedence: bulk Sender: pgsql-pkg-yum-owner@postgresql.org --001a1141c3723b0b22054290039b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable hello again. (I miss clicked and sent before finishing the last mail) So.. the tag experiment/g++4.4compilable-lw Is thought for centos6, has pgRouting 2.1 compilable with g++4.4 and it can be used with postgres9.6 and has some wrappers to use better code where possible. As a reminder I don't expect problems for CENTOS 7 and pgRouting version 2.3.1. Regards Vicky On Wed, Nov 30, 2016 at 8:49 PM, Vicky Vergara wrote= : > Hello, > I am a pgRouting developer. > I must say that I don't expect to be a problem on CENTOS 7 > > > pgRouting relies heavily on C++0x code, you can see the difference of the > things that can be done on the g++4.4 used by Centos 6 and the g++4.8 use= d > in Centos 7 > https://gcc.gnu.org/gcc-4.4/cxx0x_status.html > https://gcc.gnu.org/gcc-4.8/cxx0x_status.html > > So about Centos 6 > I dedicated some time to make a 2.1 version compilable with g++4.4 > can be found here: > https://github.com/pgRouting/pgrouting/releases/tag/experiment%2Fg%2B%2B4= . > 4compilable-lw > here you can see the usual tests we make: > https://travis-ci.org/pgRouting/pgrouting/builds/177448596 > and the tasks I made: > https://github.com/cvvergara/pgrouting/issues/60 > > I tagged it as experiment as I don't have a centos 6 to try on. > > When I compile it locally on my computer and try to link it to postgresql > I get this kind of warnings: > my guess is because postgresql I have is not compiled with 4.4 > > [ 94%] Building C object src/vrp_basic/src/CMakeFiles/vrp_basic.dir/VRP.c= .o > /home/vicky/pgrouting/pgrouting/pgrouting/src/vrp_basic/src/VRP.c: In fun= ction =E2=80=98finish=E2=80=99: > /home/vicky/pgrouting/pgrouting/pgrouting/src/vrp_basic/src/VRP.c:149: wa= rning: implicit declaration of function =E2=80=98__builtin_unreachable=E2= =80=99 > > after compilation when I start executing the tests the extension does not > load because __builtin_unreachable is not defined: > CREATE EXTENSION ERROR: could not load library > "/usr/lib/postgresql/9.3/lib/librouting-2.1.so": > /usr/lib/postgresql/9.3/lib/librouting-2.1.so: undefined symbol: > __builtin_unreachable ERROR: function pgr_version() does not exist LINE 1= : > select pgr_version() > > > > __builtin_unreachable started on GCC 4.5: > https://gcc.gnu.org/onlinedocs/gcc-4.5.4/gcc/Other-Builtins.html > > > > > > > On Wed, Nov 30, 2016 at 4:30 PM, Scott Mugnaini > wrote: > >> Any chance/possibility that 2.3.1 will make it to CentOS repo? >> http://docs.pgrouting.org/2.3/en/doc/index.html >> Thanks again, >> Scott >> >> >> On Sun, Oct 2, 2016 at 4:14 PM, Devrim G=C3=BCnd=C3=BCz wrote: >> >>> >>> Ouch. >>> >>> So, pgrouting folks are working on a new 2.2 that will includes fixes >>> for this >>> *and* gcc 4.4. I'll keep the list updated. >>> >>> Regards, Devrim >>> >>> On Fri, 2016-09-30 at 16:12 +0200, Christoph Berg wrote: >>> > Re: Devrim G=C3=BCnd=C3=BCz 2016-09-30 <1475240709.24885.136.camel@gu= nduz.org> >>> > > >>> > > >>> > > Hi Scott, >>> > > >>> > > On Fri, 2016-09-30 at 15:41 +0300, Scott Mugnaini wrote: >>> > > > >>> > > > It installs but I get error below on creating extension: >>> > > > create extension pgrouting; >>> > > > ERROR: could not load library "/usr/pgsql-9.6/lib/librouting.so"= : >>> > > > /usr/pgsql-9.6/lib/librouting.so: undefined symbol: heap_formtupl= e >>> > > >>> > > Yeah, I was working on that. This does not happen in PostgreSQL >>> > > 9.4+pgrouting >>> > > 2.0, so it must be something about PostgreSQL or so. I'll bug the >>> pgrouting >>> > > folks. >>> > >>> > commit 726117243022178e72966cbffdfb9147ec6dbbcc >>> > Author: Heikki Linnakangas >>> > Date: Thu Jul 2 21:18:04 2015 +0300 >>> > >>> > Remove obsolete heap_formtuple/modifytuple/deformtuple functions. >>> > >>> > These variants used the old-style 'n'/' ' NULL indicators. The >>> new-style >>> > functions have been available since version 8.1. That should be >>> long >>> > enough >>> > that if there is still any old external code using these >>> functions, they >>> > can just switch to the new functions without worrying about >>> backwards >>> > compatibility >>> > >>> > Peter Geoghegan >>> > >>> > >>> > >>> > Christoph >>> >>> -- >>> Devrim G=C3=9CND=C3=9CZ >>> EnterpriseDB: http://www.enterprisedb.com >>> PostgreSQL Dan=C4=B1=C5=9Fman=C4=B1/Consultant, Red Hat Certified Engin= eer >>> Twitter: @DevrimGunduz , @DevrimGunduzTR >>> >> >> > > > -- > > Georepublic UG (haftungsbeschr=C3=A4nkt) > Salzmannstra=C3=9Fe 44, > 81739 M=C3=BCnchen, Germany > > Vicky Vergara > Operations Research > > eMail: vicky@georepublic.de > Web: https://georepublic.info > > Tel: +49 (089) 4161 7698-1 > Fax: +49 (089) 4161 7698-9 > > Commercial register: Amtsgericht M=C3=BCnchen, HRB 181428 > CEO: Daniel Kastl > > > --=20 Georepublic UG (haftungsbeschr=C3=A4nkt) Salzmannstra=C3=9Fe 44, 81739 M=C3=BCnchen, Germany Vicky Vergara Operations Research eMail: vicky@georepublic.de Web: https://georepublic.info Tel: +49 (089) 4161 7698-1 Fax: +49 (089) 4161 7698-9 Commercial register: Amtsgericht M=C3=BCnchen, HRB 181428 CEO: Daniel Kastl --001a1141c3723b0b22054290039b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
he= llo again.
(I miss clicked and sent before finishing the last mail)

So.. the = tag

experiment/g++4.4compilable-lw

Is thought for centos6, has= pgRouting 2.1 compilable with g++4.4 and it can be used with postgres9.6 a= nd has some wrappers to use better code where possible.

As a reminder I don't = expect problems for CENTOS 7 and pgRouting version 2.3.1.

=

Regards

Vicky





On Wed, Nov 30, 2016 at 8:49 PM, Vicky Vergara <vi= cky@georepublic.de> wrote:
=
Hello,
I am a pgRouting develop= er.
I must say t= hat I don't expect to be a problem on CENTOS 7


pgRouting relies heavily on C++0x code, you can see the di= fference of the=20 things that can be done on the g++4.4 used by Centos 6 and the g++4.8=20 used in Centos 7
https://gcc.gnu.org/gcc-4.4/cxx0x_status.html
https://gcc.gnu.org/gcc-4.8/cxx0x_status.html

So about Centos= 6
I dedicated s= ome time to make a 2.1 version compilable with g++4.4
can be found here:
https://github.com/pgRouting/pgrouting/re= leases/tag/experiment%2Fg%2B%2B4.4compilable-lw
here you can see the usual te= sts we make:
https://travis-ci.org/pgRouting/pgroutin= g/builds/177448596
and the tasks I made:
https://github.com/cvvergara/= pgrouting/issues/60

I tagged it as experiment as I don't have a centos 6 to try= on.

=
When I compile it locally = on my computer and try to link it to postgresql I get this kind of warnings= :
my guess is be= cause postgresql I have is not compiled with 4.4

after compilation when I start executing the tests the extension does n= ot load because __builtin_unreachable is not defined:

CREATE EXTENSION ERROR: could not load library "/usr/lib/postgresql/9.3/lib/librouting-2.1.so&quo= t;: /usr/lib/postgresql/9.3/lib/librouting-2.1.so: undefined symbol: __builtin_unreach= able ERROR: function pgr_version() does not exist LINE 1: select pgr_version()


__builtin_unreachable started on = GCC 4.5:
https://gcc.gnu.org/onlinedocs/gcc-4.5.4/gcc/= Other-Builtins.html







= On Wed, Nov 30, 2016 at 4:30 PM, Scott Mugnaini <scott.mugnaini@gma= il.com> wrote:
Any chance/possibility that 2.3.1 will make it to CentOS rep= o?
http://docs.pgrouting.org/2.3/en/doc/index.html
= Thanks again,
Scott

On Sun, Oct 2, 2= 016 at 4:14 PM, Devrim G=C3=BCnd=C3=BCz <devrim@gunduz.org> = wrote:

Ouch.

So, pgrouting folks are working on a new 2.2 that will includes fixes for t= his
*and* gcc 4.4. I'll keep the list updated.

Regards, Devrim

On Fri, 2016-09-30 at 16:12 +0200, Christoph Berg wrote:
> Re: Devrim G=C3=BCnd=C3=BCz 2016-09-30 <1475240709.24885.136.camel@= gunduz.org>
> >
> >
> > Hi Scott,
> >
> > On Fri, 2016-09-30 at 15:41 +0300, Scott Mugnaini wrote:
> > >
> > > It installs but I get error below on creating extension:
> > > create extension pgrouting;
> > > ERROR:=C2=A0 could not load library "/usr/pgsql-9.6/lib= /librouting.so":
> > > /usr/pgsql-9.6/lib/librouting.so: undefined symbol: hea= p_formtuple
> >
> > Yeah, I was working on that. This does not happen in PostgreSQL > > 9.4+pgrouting
> > 2.0, so it must be something about PostgreSQL or so. I'll bug= the pgrouting
> > folks.
>
> commit 726117243022178e72966cbffdfb9147ec6dbbcc
> Author: Heikki Linnakangas <heikki.linnakangas@iki.fi>
> Date:=C2=A0=C2=A0=C2=A0Thu Jul 2 21:18:04 2015 +0300
>
> =C2=A0=C2=A0=C2=A0=C2=A0Remove obsolete heap_formtuple/modifytuple/def= ormtuple functions.
> =C2=A0=C2=A0=C2=A0=C2=A0
> =C2=A0=C2=A0=C2=A0=C2=A0These variants used the old-style 'n'/= ' ' NULL indicators. The new-style
> =C2=A0=C2=A0=C2=A0=C2=A0functions have been available since version 8.= 1. That should be long
> enough
> =C2=A0=C2=A0=C2=A0=C2=A0that if there is still any old external code u= sing these functions, they
> =C2=A0=C2=A0=C2=A0=C2=A0can just switch to the new functions without w= orrying about backwards
> =C2=A0=C2=A0=C2=A0=C2=A0compatibility
> =C2=A0=C2=A0=C2=A0=C2=A0
> =C2=A0=C2=A0=C2=A0=C2=A0Peter Geoghegan
>
>
>
> Christoph

--
Devrim G=C3=9CND=C3=9CZ
EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Dan=C4=B1=C5=9Fman=C4=B1/Consultant, Red Hat Certified Engineer<= br> Twitter: @DevrimGunduz , @DevrimGunduzTR




-= -
= 
Georepublic UG (haftungsbeschr=C3=A4nkt)
Salzmannstra=C3=9Fe 44,=20
81739 M=C3=BCnchen, Germany

Vicky Vergara
Operations Research

eMail: vicky@georepubli=
c.de
Web: https://georepu=
blic.info

Tel: +49 (089) 4161 7698-1
Fax: +49 (089) 4161 7698-9

Commercial register: Amtsgericht M=C3=BCnchen, HRB 181428
CEO: Daniel Kastl



--
= 
Georepublic UG (haftungsbeschr=C3=
=A4nkt)
Salzmannstra=C3=9Fe 44,=20
81739 M=C3=BCnchen, Germany

Vicky Vergara
Operations Research

eMail: vicky@georepubli=
c.de
Web: https://georepu=
blic.info

Tel: +49 (089) 4161 7698-1
Fax: +49 (089) 4161 7698-9

Commercial register: Amtsgericht M=C3=BCnchen, HRB 181428
CEO: Daniel Kastl
--001a1141c3723b0b22054290039b--