[Mesa-users] Unable to initialize mesasdk in Windows

[Koushik Sen]

Hi again,

I installed and updated the gcc-gfortran packages in the WSL compiler and
this is the new error message I have received.

[2018-08-20 02:24.43]  /drives/a/code
[deep1.Koushik] ➤ source /drives/a/code/mesasdk/bin/mesasdk_init.sh
mesasdk_init.sh: checking architecture
mesasdk_init.sh: unsupported architecture

But I checked the mesa_arch_check..pl file and echoed my uname which gave

 [deep1.Koushik] ➤ uname -a
CYGWIN_NT-10.0-WOW Koushik 2.7.0(0.306/5/3) 2017-02-14 23:53 i686 GNU/Linux

[deep1.Koushik] ➤ uname -s 2>/dev/null       #this is the command written
in the mesa_arch_check.pl file which is invoked in the mesasdk_init.sh file
CYGWIN_NT-10.0-WOW

So both Linux and i686 are there in uname -a but not in the uname -s
2>/dev/null. Is it a problem in extracting this information from the uname?
Can something be done now?

Yours faithfully,
Koushik

On Mon, 20 Aug 2018 at 00:39, Koushik Sen <senkoushik1995 at gmail.com> wrote:

>
>
>
> > He's specifically using the Windows Subsystem for Linux. Does MESA
>> specifically have issues with WSL, or do you just mean to say that MESA
>> doesn't run in a vanilla Windows environment?
>>
>> Yes mesa has issues with WSL, or more specifically microsoft decided not
>> to implemented certain features that are needed by mesa (and many other
>> apps its not mesa doing anything special) See here for the basic issue:
>> https://stackoverflow.com/questions/49965980/segmentation-fault-when-passing-internal-function-as-argument
>>
>
> From the stack overflow discussion, it is written that the problem is
> unlikely to be fixed anytime soon.
>
>
>>
>> > I had seen the MESA docker before installing but it was written there
>> that the MESA docker does not support all the advanced features available
>> in the Linux/Mac version. Should I switch to Linux to avoid all this
>> headache?
>>
>> You dont need to, mesa docker will be fine for all usage. The feature
>> that is missing is caching the rate/eos files but that is just an
>> optimization issue. That said i've found linux/mac better able to use all
>> cores on a system and makes things easier when you need to scale up to many
>> mesa runs on a cluster.
>>
>>
> However, Bill said that the support for windows via Docker is intended
> primarily for introductory classes using mesa.
>
>
>> Anyways, two potential problems I see are that his $PATH appears to be
>>> missing most of the standard Unix executable directories, except for /bin
>>> (perl is failing because /usr/bin is not in $PATH), and that he appears to
>>> have the SDK in the directory tree WSL uses to give Linux programs access
>>> to the Windows filesystem outside of the WSL environment (/drives, though
>>> on my WSL instance the windows drives are mounted under /mnt). There are
>>> restrictions on exactly what Linux programs can do with files outside of
>>> the WSL environment, though I can't say off the top of my head what they
>>> are, and that may be causing problems.
>>>
>>
> I used this same WSL to install an run mesa (version 6794, sdk version
> 20141212) in 2017 though, using the same commands as I have done now. It
> installed smoothly then. However, just now I tried to install it again (the
> older version) and the same set of error messages came up. For now, I think
> I will install the Mesa docker and learn the basics until I get a Linux OS
> installed.
>
> Thank you everyone for your valuable time and advise on the problem.
>
> Yours faithfully,
> Koushik
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20180820/eee0d1d0/attachment.html>