LAStools and WINE: GLU32.dll?

[Jonathan Greenberg]

Folks:

I am continuing to have no luck getting LAStools working with WINE, given that I have had to compile wine from source rather than using a package manager.  The error I keep getting is:

err:module:import_dll Loading library GLU32.dll (which is needed by L"Z:\\pathto\\lasinfo.exe") failed (error c000007b).

err:module:LdrInitializeThunk Main exe initialization for L"Z:\\pathto\\lasinfo.exe" failed, status c0000135

Any ideas?

--j

[Evon Silvia]

​Sounds like you're trying to launch the LAStools GUI, which requires GLU32.dll. ​I don't think GLU32.dll is included with the LAStools install, but it is normally part of a Windows install (c:\windows\system32 on my computer).

Since you're running on Wine, you might have to download it yourself. I believe Martin uses the venerable GLUI toolkit, which you can learn more about here: http://glui.sourceforge.net/

Evon

--
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

[Jonathan Greenberg]

Do you know how to "install" GLU32.dll? I certainly have a glu32.dll on my Windows system32 folder -- I've tried dragging it into the .wine/pathto/system32 folder, into the lastools bin directory, etc., to no avail.  Since I'm trying to do this entirely command line, I'm not sure why it even cares if I do or don't have a gui dll running.  

--j  

[Evon Silvia]

Try copying it to the LAStools bin folder, the same folder as the exe files.

You shouldn't have to do this, but I don't know much about Wine. Since you already have it in system32, your run environment's PATH variable should include a pointer to that folder, which is how you'd install it. Someone more informed should probably chime in.

As for why it's launching the GUI in the first place, I have no idea! I think it should only launch the GUI if you run the executable without any arguments.

Evon

[Martin Isenburg]

Hello,

All LAStools are linked statically against the GLU and GLUT libraries. I think that WinE may be mistaken about the GLU dependency.

Can you try to run the OpenGL,  GLU, GLUT, GLUI, and GUI-free version of LASzip that is available at

http://lastools.org/download/laszip-cli.exe

via WinE ... ? If in fact the mistaken DLL dependencies are the problem then that should work.

Martin

[Jonathan Greenberg]

Whoa, there we go:

"laszip.exe is better run in the command line or via the lastool.exe GUI

enter input file:"

Looks like it is working!  Don't even need the 32-bit nonsense dealt with.

Ok, I misunderstood your email last week, Martin.  Do you have cli versions of all of your ports, or just laszip?

--j

[Martin Isenburg]

Hello,

So it seems you have run into the same issue (i.e. WinE finds the OpenGL stubs in the code and chokes) that Kirk Waters of NOAA once struggled with (but he seems to be out of the office at the moment). However, he did manage in the end to run the tools on "head-less" servers despite the OpenGL stubs. Currently only laszip-cli.exe, lasvalidate.exe, and laslayers.exe are without GUIs ... do all of them work?

Martin

[Jonathan Greenberg]

They all appear to work without throwing the GLU32.DLL error, so it does seem the OpenGL stubs are causing the issue for a headless system.  

[Albert Godfrind]

IMO the proper solution is to run native code on each platform.  Wine is never a good solution for a production system.  

I still don't understand why some of the tools are provided as pre-built binaries exclusively for the Windows platform. That is severely limiting the appeal of LAStools IMO. 

Albert

--

Albert Godfrind

+33 6 09 97 27 23

Sent from my iPhone