This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to run offline shader compiler?

I tried running the off line shader compiler on ubuntu64, for Mali-400 target.

This fails, see below.

How can I get it to run? The malisc in top level dir does seem to work, but does not support Mali-400.

bram@Ubuntu64:~/Mali_Offline_Compiler_v4.1.0$ export MALICM_LOCATION=`pwd`

bram@Ubuntu64:~/Mali_Offline_Compiler_v4.1.0$ echo $MALICM_LOCATION

/home/bram/Mali_Offline_Compiler_v4.1.0

bram@Ubuntu64:~/Mali_Offline_Compiler_v4.1.0$ cd Mali-400/

bram@Ubuntu64:~/Mali_Offline_Compiler_v4.1.0/Mali-400$ ls -al

total 476

drwxr-xr-x 2 bram bram   4096 Feb 25 15:31 .

drwxr-xr-x 4 bram bram   4096 Feb 25 15:27 ..

-rwxr-xr-x 1 bram bram 457024 Aug 19  2013 libMali400SC.so

-rwxr-xr-x 1 bram bram  10472 Aug 19  2013 malisc

-rw-r--r-- 1 bram bram    125 Feb 25 15:31 shadow.fp

-rw-r--r-- 1 bram bram    145 Feb 25 15:31 shadow.vp

bram@Ubuntu64:~/Mali_Offline_Compiler_v4.1.0/Mali-400$ ./malisc --core=Mali-400 --vert shadow.vp

Failed to open libMali400SC.so

bram@Ubuntu64:~/Mali_Offline_Compiler_v4.1.0/Mali-400$ echo $MALICM_LOCATION

/home/bram/Mali_Offline_Compiler_v4.1.0

bram@Ubuntu64:~/Mali_Offline_Compiler_v4.1.0/Mali-400$ ./malisc --core=Mali-400 --vert shadow.vp

Failed to open libMali400SC.so

bram@Ubuntu64:~/Mali_Offline_Compiler_v4.1.0/Mali-400$ ldd ./libMali400SC.so

  linux-vdso.so.1 =>  (0x00007fff897d2000)

  libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f0b8ccad000)

  /lib64/ld-linux-x86-64.so.2 (0x00007f0b8d302000)

bram@Ubuntu64:~/Mali_Offline_Compiler_v4.1.0/Mali-400$

  • Hi bram,

    Thanks for the report.

    The reason Offline Shader Compiler for ARM Mali-400 doesn't work is that it fails to load libMali400SC.so.

    Please try following commands:

    cd Mali-400/

    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:`pwd`

    ./malisc --core=Mali-400 --vert shadow.vp

    That should solve your problem.

    I will raise this issue internally to make sure it is documented in the User Guide for the next release.

    Thanks,

    Jacek