libspatialindex has to be new enough to have a *working* C API, because that's what Firedrake uses.

That HEAD is from *our* git repository clone so this is a known working version.

I'm not sure what goes exactly wrong when this issue happens with gtest, the install script explicitly patches Makefile.am ( https://github.com/firedrakeproject/firedrake/blob/master/scripts/firedrake-install#L718 ) to avoid building the test suite which would require gtest.

Try to debug what is going on with that one. Is that patch applied? Why is it trying to use gtest?

Hi,

Can the firedrake install script be modified to use a different version of lbspatialindex ?

Given the error meesage below.

Some files from the gtest are missing.

It can build by hand but that requires an modification with every update.

Best wishes,

Onno & Tim

From: IT Service Desk <leeds@service-now.com>
Sent: Tuesday, November 14, 2017 11:38 AM
To: Onno Bokhove
Subject: REQTSK0145114 - IT request - Install software - Firedrake (Mac)

Dear Onno,

The firedake-install script fails to complete as there appears to be an error in the

configuration of the libspatialindex code which the script doesn't handle:

libspatialindex/test/gtest/gtest-1.7.0:config.status:1140: error: cannot find input file: Makefile.in

gtest doesn't appear to be used as libspatialindex compiles without it (outside of the firedrake-install script).

Is there a way to get the firedake-install script to use a different version of libspatialindex rather

than downloading the head from the git repository every time.

Regards,

Tim.

IT Service Desk

University of Leeds

t: 0113 343 3333

@ITServicesUoL

For support and online information please visit: http://it.leeds.ac.uk

We welcome any feedback about our service. Just visit https://leeds.onlinesurveys.ac.uk/it-service-desk-feedback