Helmut Kudrnovsky wrote >>Not that I know how to fix that, but what needs to be done? > > have look into > > 32bit issues: > > https://trac.osgeo.org/osgeo4w/ticket/429 > https://trac.osgeo.org/osgeo4w/ticket/539 > > 64bit issues: > > https://trac.osgeo.org/osgeo4w/ticket/550 > > the liblas [1] tools and laszip in OSGeo4W are broken. > > what would be needed: someone may investigate the issues a little bit more > and may recompile these tools from scratch that they are working again. it > seems to be some kind of dll mismatches with different flavours in 32bit > and > 64bit. > > [1] https://www.liblas.org/
deactivated now lidar modules in winGRASS 32bit and 64bit by: [GRASS-SVN] r71920 - grass/trunk/mswindows/osgeo4w svn_grass at osgeo.org [GRASS-SVN] r71921 - grass/branches/releasebranch_7_4/mswindows/osgeo4w svn_grass at osgeo.org [GRASS-SVN] r71922 - grass/trunk/mswindows/osgeo4w svn_grass at osgeo.org [GRASS-SVN] r71923 - grass/branches/releasebranch_7_2/mswindows/osgeo4w svn_grass at osgeo.org in a mid term, a fix of the liblas/libzip tools in OSGeo4W is needed. or in the long term a switch to pdal may be a choice: https://trac.osgeo.org/grass/ticket/2732 ----- best regards Helmut -- Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev