Mac OS X, Wine, and LAStools

[Greg P]

Hello and good health to you.
I am using a Macbook Pro running OS X 10.13.1 (High Sierra). I am using Wine version 2.0.3.
I have read about using Wine to run LAStools on a Mac. (See Using LAStools on Mac OS X with Wine, including comments.)
My folder Applications/LAStools/bin looks like first picture below.
Whether I invoke the tool (let's use lasview.exe for example) by command line (in a terminal window) or by double-clicking, I get the result shown in the 2nd picture below.
I have saved the "backtrace" as a six-page text file. Please see attached file above. I don't know how to interpret the information.
I guess that somehow my installation of Wine is not correct; somehow it is not connecting properly with the LAStools.
I have tried using LAStools through QGIS (version 2.18.1). The tools, such as lasview, appear to run, but no results appear. With tools that should have an output file - i.e., lasclip - there is no apparent output.
How do I trouble-shoot this problem?

[Albert Godfrind]

From the stack trace, the exception is thrown by the strtod() C library function. This is the function that converts a string containing a number with decimals to a floating point double. The exception is a memory fault (trying to access address 0). An initialized pointer ? 

But then also: 

Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0xa7572d04).

Are the lastools compiled as 32-bit code ? Macs are obviously running full 64-bit (hardware, OS and libraries) ? Or maybe you run a 32-bit version of wine ? 

Albert

--
Albert Godfrind | Geospatial and Graph technologies | Tel: +33 4 37 43 47 27 | Mobile: +33 6 09 97 27 23 | Twitter: @agodfrin
Oracle Server Technologies
Centre Régus - Les Algorithmes - Bâtiment ARISTOTE A | 2000 Route des Lucioles | 06410 Sophia Antipolis | France

Everything you ever wanted to know about Oracle Spatial

--
Download LAStools at
http://lastools.org
http://rapidlasso.com
Be social with LAStools at
http://facebook.com/LAStools
http://twitter.com/LAStools
http://linkedin.com/groups/LAStools-4408378
Manage your settings at
http://groups.google.com/group/lastools/subscribe
<Wine_error_message_backtrace_02.txt>

[Greg P]

Thank you for replying.

How do I find out whether the lastools are compiled as 32-bit code?

How do I find out whether my version of Wine is 32-bit?

Are you suggesting that the 32-bit-ness of something is disabling the Wine program?

Again, thank you.

[Kirk Waters - NOAA Federal]

Greg,

LAStools is definitely compiled as 32-bit code. If it's not working, it's very likely that your wine version is 64-bit. I had that same problem with RHEL7. Some searching online lead to instructions for compiling wine with both 32-bit and 64-bit capabilities. There may be similar info out there for doing that with OS X.

Kirk Waters, PhD                     | NOAA Office for Coastal Management

Applied Sciences Program      | 2234 South Hobson Ave
843-740-1227                          | Charleston, SC 29405    

coast.noaa.gov/digitalcoast

[Albert Godfrind]

This page: https://wiki.winehq.org/FAQ#Wineprefixes (see section 6.35) says: 

6.5.3 How do I create a 32 bit wineprefix on a 64 bit system?

At present there are some significant bugs that prevent many 32 bit applications from working in a 64 bit wineprefix. To work around this, you can create a new 32 bit wineprefix using the WINEARCH environment variable. In a terminal, type:

WINEARCH=win32 WINEPREFIX=path_to_wineprefix winecfg 

(use the actual path to the wineprefix) Do not use an existing directory for the new wineprefix: Wine must create it.

Once a 32 bit wineprefix is created, you no longer have to specify WINEARCH in the command line to use it, as the architecture of an existing wineprefix cannot be changed. Note that if the wineprefix is not the default (~/.wine, you do have to specify the WINEPREFIX variable when installing anything (including winetricks) to it:

WINEPREFIX=path_to_wineprefix wine start /unix path_to_installer

Not sure if it is relevant, but maybe worth a try …

Then again, a better answer would probably be to build all lastools binaries in 64-bit. Who runs 32-bit OS’s nowadays ?

Albert 

--
Albert Godfrind | Geospatial and Graph technologies | Tel: +33 4 37 43 47 27 | Mobile: +33 6 09 97 27 23 | Twitter: @agodfrin
Oracle Server Technologies
Centre Régus - Les Algorithmes - Bâtiment ARISTOTE A | 2000 Route des Lucioles | 06410 Sophia Antipolis | France

Everything you ever wanted to know about Oracle Spatial

[Greg P]

Thank you for your generous help!

I created a 32-bit wine prefix and named it "~/.wine" which, I understand, makes the 32-bit prefix the default when I run an application with Wine.
I still got the same error message ("The program lasview.exe has encountered a serious problem and needs to close. ...This can be caused by a problem in the program or a deficiency in Wine. You may want to check the Application Database for tips about running this application.") I will try to attach the "backtrace" to this response. But I have no idea how to glean useful diagnostic information from the backtrace.

I looked on WineHQ Applications Database, but there seems to be nothing about LAStools (except the query I posted quite some time ago, and to which no one has responded).

I've read of something called "Winetricks". Could that be a path worth investigating for LAStools and Wine?

Again, thank you.

Greg P