[postgis-devel] PostGIS 2.2.6, 2.3.4, and 2.4.1
pramsey at cleverelephant.ca
Fri Oct 20 08:57:58 PDT 2017
If your process starts with ./autogen.sh then you won't notice this
problem, because *your* call to glibtoolize will put install-sh into place.
If you start with ./configure however, you'll notice it. The configure-only
workflow exists because traditionally projects (a) didn't want to force
builders to install all the autotools and (b) autotools changed behaviour
enough that relying on whatever combo of autotools folks might have
resulted in unpredictable results compared to just including a pre-built
configure script in your tarball.
On Fri, Oct 20, 2017 at 8:54 AM, Regina Obe <lr at pcorp.us> wrote:
> Is this something that doesn't effect everyone using the tar ball?
> I just tested my build from tar ball script -- building the 2.4.1 that
> Paul packaged.
> My build/install from tar ball script doesn't have an autogen.sh step, yet
> it built and installed fine and I can confirm I can do CREATE EXTENSION
> postgis VERSION "2.4.1" after
> -----Original Message-----
> From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On
> Behalf Of Sebastiaan Couwenberg
> Sent: Friday, October 20, 2017 5:48 AM
> To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
> Subject: Re: [postgis-devel] PostGIS 2.2.6, 2.3.4, and 2.4.1
> On 10/20/2017 10:31 AM, Devrim G�nd�z wrote:
> > configure: error: cannot find install-sh, install.sh, or shtool in "."
> "./.." "./../.."
> Just run autogen.sh before configure.
> Retooling the build system is a packaging best practice any way.
> Kind Regards,
> GPG Key ID: 4096R/6750F10AE88D4AF1
> Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the postgis-devel