Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aHKDA-0006WQ-0d for pgsql-pkg-yum@arkaria.postgresql.org; Thu, 07 Jan 2016 23:43:20 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aHKD9-0003mO-F7 for pgsql-pkg-yum@arkaria.postgresql.org; Thu, 07 Jan 2016 23:43:19 +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) (envelope-from ) id 1aHKD9-0003mH-05 for pgsql-pkg-yum@postgresql.org; Thu, 07 Jan 2016 23:43:19 +0000 Received: from ns3.gunduz.org ([107.170.88.27] helo=ns1.gunduz.org) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aHKD2-0006qs-57 for pgsql-pkg-yum@postgresql.org; Thu, 07 Jan 2016 23:43:17 +0000 Received: from asus-laptop-03.gunduz.org (unknown [85.99.241.196]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ns1.gunduz.org (Postfix) with ESMTPSA id 0949F4045D; Thu, 7 Jan 2016 23:43:09 +0000 (UTC) Message-ID: <1452210185.21916.77.camel@gunduz.org> Subject: Re: Question about the toolchain (CGAL / SFCGAL related) From: Devrim =?ISO-8859-1?Q?G=DCND=DCZ?= To: John Harvey , pgsql-pkg-yum Date: Fri, 08 Jan 2016 01:43:05 +0200 In-Reply-To: References: Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-8c+BOirz3nHtJ0zNsLCx" X-Mailer: Evolution 3.18.3 (3.18.3-1.fc23) Mime-Version: 1.0 X-Pg-Spam-Score: -1.9 (-) 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 --=-8c+BOirz3nHtJ0zNsLCx Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, On Thu, 2016-01-07 at 17:43 -0500, John Harvey wrote: > H > I'm having a bit of trouble building SFCGAL / CGAL, and I wanted to > ask a > couple of questions about the toolchain used to build the code. > Specifically, I was wondering about builds on EL-6. I could not build SFCGAL on RHEL 6, due to boost issues, which you also encountered. > 1) For EL-6 builds, what version of rpmbuild is installed (and how is > it installed)? > The latest version I found via yum install is 4.8. =C2=A0Other than that, we don't use any toolchain which is not included in the repo. If we make an exception, we add it to our repo. $ rpm -qv rpm-build rpm-build-4.8.0-47.el6.x86_64 > With the spec-file as written, I encounter the following build errors > on > SFCGAL: >=20 > =C2=A0=C2=A0=C2=A0=C2=A0File must begin with "/": GLPLv2 > =C2=A0=C2=A0=C2=A0=C2=A0File must begin with "/": LICENSE >=20 > From my research, this happens because non-absolute paths were added > in RPM 4.11.=C2=A0=C2=A0So, the 4.8 standard install causes problems. Err, actually it is the new %license macro that was introduced recently, and I forgot to add conditionals. See line 50 in here as an example of what I missed: http://git.postgresql.org/gitweb/?p=3Dpgrpms.git;a=3Dblob;f=3Drpm/redhat/9.= 5/ pgcenter/EL- 6/pgcenter.spec;h=3Dde5f77709b0be85bbc7bd50bbc8678b4609247ef;hb=3Df5c0cfbbf 53c0a9b69689b3e4034c8fb44620e7f#l50 > 2) For EL-6 builds, what version of boost-devel is installed (and how > is it installed)? As above: We all stick to OS supplied packages, so: $ rpm -qv boost-devel boost-devel-1.41.0-27.el6.x86_64 We also use EPEL repo a lot. > It seems like Boost is a tricky thing on EL-6.=C2=A0=C2=A0The latest RPM = that > is > available for installation is 1.41.0.=C2=A0=C2=A0However, without a later > version, there's a compile error on CGAL 4.7: >=20 > /usr/include/CGAL/Kd_tree.h:34:37: fatal error: > boost/container/deque.hpp: No such file or directory Yep, I got the same. > From what I gather, deque.hpp has been relocated elsewhere in code > for later versions of boost.=C2=A0=C2=A0And, while there is a boost148 pa= ckage > available, it unfortunately puts the Boost include files into > /usr/include/boost148 instead of /usr/include/boost.=C2=A0=C2=A0Unless th= ere's > a way to notify the build of this differing path, the only workaround > that I've found is to build a new version of boost (i.e. 1.53.0 from > source).=C2=A0=C2=A0So I'm curious how the PGDG toolchain handles this ca= se. We don't do it, as it will break more dependencies. For the same reason, we disabled raster support on RHEL 6 RPMs. Regards, --=20 Devrim G=C3=9CND=C3=9CZ Principal Systems Engineer @ EnterpriseDB: http://www.enterprisedb.com PostgreSQL Dan=C4=B1=C5=9Fman=C4=B1/Consultant, Red Hat Certified Engineer Twitter: @DevrimGunduz , @DevrimGunduzTR --=-8c+BOirz3nHtJ0zNsLCx Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJWjvgJAAoJENjDPf6Sz261/u8QAIUadrPkIwukaZR4Ek49XM79 yXaLhDrrjD8VGwZC8ksS+Mh+zIKm7JxMfh9PjBDYEMntihcLVsaEoLd8MHCaKAgf qH5wi5gTYo9vXYiZCjK2tJlcAFJvvXJ/4VouixgnqgfaoWrngdOAsAnapLPIGb+S O5jNgZkpH/nEe0DOhDvZ3+kgKwUnM7h69CVzNZSFe8K7RlzLVI2mgjXPdHC7qXWg I7H//V5AFGwabxwqeR+Oyi30tj0/QEeEVmqOcKqOsbgb2aVSaRKcL3/dXvSxkmBF XnjsT7mEUILL4v4WihfX1b2iT9EW75OOQMpp16yu3hipj3o69nSUVg4HOxc3j7dz R2sNmdTSeTmE8K7lKP+LWkZOogvT029a33USB2k44yj9gtVPAALHLLBXg0XmTCHd C94m7Cg84Y6+PwE3lImL8o3w64JYIu4VZev2tCWKW0WJsJLRQHzyMoOjIRZiLzHH 9nJKDwqFVJg9acU1baVh0IhPRx24tnnXZw9Og2eSyhPeFsPPQMS02gFAxQIkC95V TA6DCRu3u9wl0Gnayxv/gU2lS/hJQOLGmIHcNRFvVCb5aKzYBlk3if4es2a7DRBj /+nZWeloM2/zoM2HA9Soio1hqgZ46kJj7J5dVIrKQDLu2mAisxTcp5lJvJtWX9ow C45nFmNx/krZx8wnxlko =J9Vq -----END PGP SIGNATURE----- --=-8c+BOirz3nHtJ0zNsLCx--