Problems loading maya with a custom shader - "undefined symbol: AiNodeParamStr"

[riegerXW6EJ]

Hello,

A stundent at our faculty has developed some simple shader for Arnold and it already worked well in Maya 2017. Just installed Maya 2017 on another machine (Ubuntu Linux, as used before) and when starting Maya it loads up until trying to load the shader. Then it will crash with the message

/usr/autodesk/maya2017/bin/maya.bin: symbol lookup error: /opt/solidangle/mtoa/2017/shaders/shader_bsdf_ptm.so: undefined symbol: AiNodeParamStr

Worked before on the other machine and the same shader works well with kick as a renderer for testing. Any idea why it could be that AiNodeParamStr isn't found? Should normally be in the libai, right? Shader is build and linked to Arnold 5.0.1.4 SDK with the current MtoA installed for Maya.

[Stephen.Blair]

What MtoA do you have? I bet you have an old one that uses Arnold 5.0

You can also use kick -nodes on the command line, then you'll see some message about incompatible versions.

[riegerXW6EJ]

Both installed yesterday and seem to be the same version. Also when I use kick from /opt/solidangle/mtoa/2017/bin/kick it also renders with this shader compilation. Before I had the problem that MtoA was older and I got the message from MtoA that MtoA is older than the used SDK.

[Stephen.Blair]

Can you post a full Arnold log for a render? Or set MTOA_STARTUP_LOG_VERBOSITY to 2 and post a startup log?

Or, from a Maya session, run ldd on shader_bsdf_ptm.so

[riegerXW6EJ]

Seems I found the problem. Just reordered the gcc parameters. I had "-L$ARNOLD_PATH/bin -lai" in front of the source files and found that my old makefile before a rewrite had them at the back and still worked without any parameter changed. Didn't knew that the order in this regards is important to gcc.

Used to Cmake where I don't care about building the gcc command line myself.