Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cCHRl-0001b3-Vd for pgsql-pkg-yum@arkaria.postgresql.org; Thu, 01 Dec 2016 02:50:06 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cCHRl-00045X-9J for pgsql-pkg-yum@arkaria.postgresql.org; Thu, 01 Dec 2016 02:50:05 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cCHRh-0003x2-9j for pgsql-pkg-yum@postgresql.org; Thu, 01 Dec 2016 02:50:01 +0000 Received: from mail-io0-x232.google.com ([2607:f8b0:4001:c06::232]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1cCHRc-0002eG-MQ for pgsql-pkg-yum@postgresql.org; Thu, 01 Dec 2016 02:50:00 +0000 Received: by mail-io0-x232.google.com with SMTP id c21so363051787ioj.1 for ; Wed, 30 Nov 2016 18:49:56 -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=oaFwlP68+3uIUsLYHUckSQveUEtASE3kE9kKQ16Upn0=; b=jfQ4N+ZEbXy30gP8F9k0ir2Raeffo3h+l0iUCnsVCYg4m6Oc5N0UfEUSbG2Q+ELFYE 0JHJsvbTwTtelrpPEcHwcIjD4n6MJ8WYwotxsKrys7ZKpNLPiZt9gEdlvFznUyRVmz23 y5348VM0WOHmCPmusXfp1SS8wxlUIOGnAettBztmOKTO441H9/DXinwSjSlDXJSRDN8W KyyPPxHQcceXhF5kJ+zF/PurS1w4pW4yadtVCimTM2ZxTBVbZbxbHAjGRWi0xhXu4kNh r8wN73Hcob2obsr8i0x20d/vtpfPtsvBaqpLt5egSgsSaGTpAaw/oY3UvnmI4VxboDsA SucQ== 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=oaFwlP68+3uIUsLYHUckSQveUEtASE3kE9kKQ16Upn0=; b=hyUapBW9Jfk6wHDjXzZ0vOYOVNx7PuT07iI5eNCtxGBDGa8b9mP7Zp0oAvtUHjwCYd ZNy4RNXurgoPeDvmJBb5Kb18f4807iyEzOLZy8XEWts8HflQ3D0T57HEsxlu0yKI4BJU hhdtZ9PbTMECUS+b+ys5ZeR6YB5px5IrPg3qp0j9v8INrXLZN8t9t9gUXpwYPTwDm4Na uxEvY0CsbDf8qvSkaJkQEqWhw1sPo7VmAOCaXHSj3Q5m+XhxSKdhLFyG9/W2dr8auWOt 7W/UGLUMq02jcYUtyb5tOnhZZIV6quCtLWbRk+8CHSv4aXivSh7UhTmQQDXYgXrI7W4t f9nA== X-Gm-Message-State: AKaTC003gs1PSxsYR9hPD2pemstZoCcEoHsf8T+klphNig8SBh8w4saQzwZb9/DQVlC6FUgl+O//aONCT6K/xA== X-Received: by 10.107.32.141 with SMTP id g135mr23616132iog.96.1480560592234; Wed, 30 Nov 2016 18:49:52 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.144.17 with HTTP; Wed, 30 Nov 2016 18:49:51 -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:49:51 -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=001a1141c3722b49f005428fe000 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 --001a1141c3722b49f005428fe000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 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 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.4= compilable-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 function =E2=80=98finish=E2=80=99: /home/vicky/pgrouting/pgrouting/pgrouting/src/vrp_basic/src/VRP.c:149: warning: 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 fo= r >> 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@gun= duz.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_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 >> > 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 lo= ng >> > 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 Engine= er >> Twitter: @DevrimGunduz , @DevrimGunduzTR >> > > --=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 --001a1141c3722b49f005428fe000 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
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.o= rg/gcc-4.4/cxx0x_status.html
https://gcc.gnu.o= rg/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/releases/tag/experiment%2= Fg%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.
<= /font>

When I compile it locally on my com= puter and try to link it to postgresql I get this kind of warnings:
my guess is because pos= tgresql 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 funct=
ion =E2=80=98finish=E2=80=99:
/home/vicky/pgrouting/pgrouting/pgrouting/src/vrp_basic/src/VRP.c:149: warn=
ing: implicit declaration of function =E2=80=98__builtin_unreachable=E2=80=
=99

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": /usr/lib/postgresql= /9.3/lib/librouting-2.1.so: undefi= ned 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 <scott.mugnaini@gmail.com> w= rote:
Any chan= ce/possibility that 2.3.1 will make it to CentOS repo?
http://docs.pg= routing.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 <= devrim@gunduz.org> wrote:
<= br> 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
--001a1141c3722b49f005428fe000--