[GRASS-dev] Compilation of most addons fails on build server

Hi,

Most addons don't compile on the windows build server, all with a message such as:

"Makefile:7: /home/landa/src/grass74_release/dist.x86_64-pc-linux-gnu/include/Make/Script.make: No such file or directory
Makefile:8: /home/landa/src/grass74_release/dist.x86_64-pc-linux-gnu/include/Make/Python.make: No such file or directory
make: *** No rule to make target '/home/landa/src/grass74_release/dist.x86_64-pc-linux-gnu/include/Make/Python.make'. Stop."

or

"Makefile:5: /home/landa/src/grass74_release/dist.x86_64-pc-linux-gnu/include/Make/Script.make: No such file or directory
make: *** No rule to make target '/home/landa/src/grass74_release/dist.x86_64-pc-linux-gnu/include/Make/Script.make'. Stop."

That means the man pages are not accessible either (maybe we could have a system that if building fails, the man page from the last successfully compiled version is displayed ?).

Trying to see the build logs on Linux [1], I get an "Insecure connection" error:

"wingrass.fsv.cvut.cz uses an invalid security certificate. The certificate expired on 17/07/18 11:36. The current time is 20/07/18 11:31."

Moritz

[1] https://wingrass.fsv.cvut.cz/grass74/x86/addons/latest/logs/

On 20/07/18 11:34, Moritz Lennert wrote:

Hi,

Most addons don't compile on the windows build server, all with a
message such as:

"Makefile:7:
/home/landa/src/grass74_release/dist.x86_64-pc-linux-gnu/include/Make/Script.make:
No such file or directory
Makefile:8:
/home/landa/src/grass74_release/dist.x86_64-pc-linux-gnu/include/Make/Python.make:
No such file or directory
make: *** No rule to make target
'/home/landa/src/grass74_release/dist.x86_64-pc-linux-gnu/include/Make/Python.make'.
   Stop."

or

"Makefile:5:
/home/landa/src/grass74_release/dist.x86_64-pc-linux-gnu/include/Make/Script.make:
No such file or directory
make: *** No rule to make target
'/home/landa/src/grass74_release/dist.x86_64-pc-linux-gnu/include/Make/Script.make'.
   Stop."

That means the man pages are not accessible either (maybe we could have
a system that if building fails, the man page from the last successfully
compiled version is displayed ?).

Trying to see the build logs on Linux [1], I get an "Insecure
connection" error:

Sorry, this should have been "build logs on Windows"

"wingrass.fsv.cvut.cz uses an invalid security certificate. The
certificate expired on 17/07/18 11:36. The current time is 20/07/18 11:31."

Moritz

[1] https://wingrass.fsv.cvut.cz/grass74/x86/addons/latest/logs/
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev