[Mesa-users] Unable to initialize mesasdk in Windows

[Rob Farmer]

 > 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

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

> Has the initialisation scheme changed for mesasdk from 2017?
> bash: /drives/a/code/mesasdk/bin/mesasdk_arch_check.pl
<http://disq.us/url?url=http%3A%2F%2Fmesasdk_arch_check.pl%3A-lwHYLIeyly0M94TgTYcUKOpPT0&cuid=4982355>:
/usr/bin/perl: bad interpreter: No such file or directory

No, but your missing perl from your environment

Rob


On Sun, 19 Aug 2018 at 17:31, Jon Brase <jon.brase 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?
>
> 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.
>
>
> -------- Original message --------
> From: Rob Farmer <r.j.farmer at uva.nl>
> Date: 8/19/2018 09:51 (GMT-06:00)
> To: senkoushik1995 at gmail.com
> Cc: mesa-users <mesa-users at lists.mesastar.org>
> Subject: Re: [Mesa-users] Unable to initialize mesasdk in Windows
>
> Hi
>
> MESA does not run under windows. Your best bet is to download mesa-docker
> https://github.com/evbauer/MESA-Docker and follow the instructions there
>
> Rob
>
> On Sun, 19 Aug 2018 at 15:57, Koushik Sen via Mesa-users <
> mesa-users at lists.mesastar.org> wrote:
>
>> Hi,
>>
>>
>> My name is Koushik, I am going to start my PhD studies in the group of
>> Norbert Langer from November.
>>
>>
>> I am trying to install the new version of MESA and I am getting the
>> attached error statements when I am trying to initialize mesasdk, after I
>> have downloaded and unzipped the mesasdk file. I have tried to install
>> older versions of mesasdk as well (20141212) but the same error message was
>> getting displayed. Below are the sequence of lines.
>>
>>
>> [2018-08-19 18:49.45] /drives/a/code
>> [deep1.Koushik] ➤ export MESASDK_ROOT=/drives/a/code/mesasdk
>> ─
>>
>> [2018-08-19 18:59.20] /drives/a/code
>> [deep1.Koushik] ➤ source /drives/a/code/mesasdk/bin/mesasdk_init.sh
>> <http://disq.us/url?url=http%3A%2F%2Fmesasdk_init.sh%3ANuL3r33PnGEMQVVyaclI6RjXfrY&cuid=4982355>
>> mesasdk_init.sh
>> <http://disq.us/url?url=http%3A%2F%2Fmesasdk_init.sh%3ANuL3r33PnGEMQVVyaclI6RjXfrY&cuid=4982355>:
>> checking architecture
>> bash: /drives/a/code/mesasdk/bin/mesasdk_arch_check.pl
>> <http://disq.us/url?url=http%3A%2F%2Fmesasdk_arch_check.pl%3A-lwHYLIeyly0M94TgTYcUKOpPT0&cuid=4982355>:
>> /usr/bin/perl: bad interpreter: No such file or directory
>> bash: [: !=: unary operator expected
>> mesasdk_init.sh
>> <http://disq.us/url?url=http%3A%2F%2Fmesasdk_init.sh%3ANuL3r33PnGEMQVVyaclI6RjXfrY&cuid=4982355>:
>> checking prerequisites
>> mesasdk_preq_check.sh
>> <http://disq.us/url?url=http%3A%2F%2Fmesasdk_preq_check.sh%3APbnR9DVu0OIBCf_a612RZMef4LQ&cuid=4982355>:
>> error: no acceptable C compiler found in $PATH
>> See `config.log' for more details.
>> mesasdk_init.sh
>> <http://disq.us/url?url=http%3A%2F%2Fmesasdk_init.sh%3ANuL3r33PnGEMQVVyaclI6RjXfrY&cuid=4982355>:
>> regenerating headers
>> ./fixinc.sh
>> <http://disq.us/url?url=http%3A%2F%2Ffixinc.sh%3AUkRQIJ65oZj29L7yRb_5YpJRcG4&cuid=4982355>:
>> line 431:
>> /drives/a/code/mesasdk/libexec/gcc/x86_64-pc-linux-gnu/7.2.0/install-tools/fixincl:
>> cannot execute binary file
>>
>> Version of MESA: 10398
>> Version of mesasdk: x86_64-linux-20180127
>> Platform: Laptop, Windows 10, Bourne Shell
>>
>> ─
>> [2018-08-19 19:08.37] /drives/a/code
>> [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] ➤ gfortran -v
>> /drives/a/code/mesasdk/bin/gfortran: line 49:
>> /drives/a/code/mesasdk/bin/gfortran.exec: cannot execute binary file
>>
>> [deep1.Koushik] ➤ echo $MESASDK_ROOT
>> /drives/a/code/mesasdk
>>
>> [deep1.Koushik] ➤ echo $PATH
>>
>>
>> /drives/a/code/mesasdk/bin:/bin:/drives/c/Users/deep1/DOCUME~1/MobaXterm/slash/bin:/drives/c/WINDOWS:/drives/c/WINDOWS/system32
>>
>>
>> I would be grateful to anyone who can help me get around this problem.
>>
>>
>> Yours faithfully,
>>
>> Koushik
>> _______________________________________________
>> mesa-users at lists.mesastar.org
>> https://lists.mesastar.org/mailman/listinfo/mesa-users
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20180819/fa40f53f/attachment.html>