[GRASS-dev] [GRASS-user] WinGRASS build up (WIP)

GRASS GRASS developer
,
21

Hi Jurgen and Helmut,

I’d uninstalled everything related with QGIS, GRASS, GDAL, GMT, etc, and installed again from OSGeo4W.

At the final stages of OSGeo4W installation, I get the same curl_mime_init error with crssync.exe, but referring to gdal301.dll (image attached).

Jürgen E. Fischer <jef@norbit.de> escreveu no dia sábado, 16/11/2019 à(s) 14:32:

Hi Helmut,

On Sat, 16. Nov 2019 at 15:22:32 +0100, Jürgen E. Fischer wrote:

That update is unrelated.

Oh, I didn’t see the screen shot - maybe the update helps - but it was
at least not done for this.

Jürgen

–
Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50
Software Engineer D-26506 Norden https://www.norbit.de
QGIS release manager (PSC) Germany IRC: jef on FreeNode

grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

(attachments)

osgeo4w_gdal301.jpg

22

I'd
uninstalled everything related with QGIS, GRASS, GDAL, GMT, etc, >and

installed again from OSGeo4W.

At t
he final stages of OSGeo4W installation, I get the same >curl_mime_init

error with crssync.exe, but referring to gdal301.dll >(image attached).

Are you installing OSGeo4W stack with the exp/testing tick activated? It
looks like as you're installing gdal-dev/gdal301.dll according to the
screenshot.

Then it could be that some library mixing/mismatch may happen.

Try to install a fresh OSGeo4W in normal mode only for winGRASS 7.8.1, then
try to start winGRASS.

In the windows Explorer, search in c:\windows for curl and report back if
you find some curl binary there.

-----
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html

23

Hi Helmut,

gdal-dev was because I was also installing QGIS 3.10. But without QGIS 3.10 and gdal-dev, I get the same gdal300.dll error in GRASS 7.8.1.

The search for curl in c:\windows shows many results (please see images attached). I start to believe that this can be some local mismatch or conflict with a past installation of some other software that used curl and gdal.

Thank you very much for your help!

Best regards,
Pedro

Helmut Kudrnovsky <hellik@web.de> escreveu no dia sábado, 16/11/2019 à(s) 16:45:

I’d
uninstalled everything related with QGIS, GRASS, GDAL, GMT, etc, >and
installed again from OSGeo4W.

At t
he final stages of OSGeo4W installation, I get the same >curl_mime_init
error with crssync.exe, but referring to gdal301.dll >(image attached).

Are you installing OSGeo4W stack with the exp/testing tick activated? It
looks like as you’re installing gdal-dev/gdal301.dll according to the
screenshot.

Then it could be that some library mixing/mismatch may happen.

Try to install a fresh OSGeo4W in normal mode only for winGRASS 7.8.1, then
try to start winGRASS.

In the windows Explorer, search in c:\windows for curl and report back if
you find some curl binary there.

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

(attachments)

c_win_curl_1.jpg
c_win_curl_4.jpg
c_win_curl_2.jpg
c_win_curl_3.jpg

24

gdal-dev was because I was also installing QGIS 3.10.

checking here:

QGIS version 3.10.0-A Coruña
Compiled against Qt 5.11.2
Compiled against GDAL/OGR 3.0.2 <=
Compiled against GEOS 3.8.0-CAPI-1.13.1
Compiled against SQLite 3.29.0
PostgreSQL Client Version 11.5

3.10.0 is now available in OSGeo4W without the need to install gdal-dev

The search for curl in c:\windows shows many results (please see images

attached). I start to believe >that

this can be some local mismatch or conflict with a past installation of

some other software that used curl >and gdal

yes it looks like that.

are you using windows 10, right? windows 10 ships curl since about 1 year or
so [1].

I compared your explorer search results here with mine on a windows 10 box.

in
https://lists.osgeo.org/pipermail/grass-dev/attachments/20191116/8570c76d/attachment-0005.jpg

there are 2 libcurl.dlls from 2016.

I don't have them in my win 10 box. not sure if you have admin rights on
your box, but you can rename them and then try to start winGRASS again.

[1] https://daniel.haxx.se/blog/2018/01/13/microsoft-curls-too/

-----
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html

25

Hi Helmut,

checking here:

QGIS version 3.10.0-A Coruña
Compiled against Qt 5.11.2
Compiled against GDAL/OGR 3.0.2 <=
Compiled against GEOS 3.8.0-CAPI-1.13.1
Compiled against SQLite 3.29.0
PostgreSQL Client Version 11.5

3.10.0 is now available in OSGeo4W without the need to install gdal-dev

I’m using nightly builds (qgis-rel-dev), and this one needs gdal-dev.

QGIS version 3.10.0-A Coruña
QGIS code revision 1ffa829539
Compiled against GDAL/OGR 3.1.0dev
Running against GDAL/OGR 3.1.0dev

I compared your explorer search results here with mine on a windows 10 box.

in
https://lists.osgeo.org/pipermail/grass-dev/attachments/20191116/8570c76d/attachment-0005.jpg

there are 2 libcurl.dlls from 2016.

I don’t have them in my win 10 box. not sure if you have admin rights on
your box, but you can rename them and then try to start winGRASS again.

Perfect!!! These libcurl.dlls were the problem! More precisely, the one on System32. After changed their names, everything works again! Issue solved!

Thank you very very much for your help and persistence Helmut!

Best regards,
Pedro Venâncio