Can you be more specific? I think you can build Elemental, but your difficulty is in linking it to your profiling tool. Can you verify that you can build Elemental?
We have two open bugs on building/linking Elemental on the SCC. We know that Elemental as itself works fine on the SCC. The two open bugs are
Xu, how are these bugs related? Can they be combined?
Thanks for your reply. Well I can build Elemental but I cannot build it to a statically-linked executable. The two bugs have some relationship but not the same. The first one shows the bugs when I tried to link Elemental with our tool. But the second bug should be solved first. We should first create a statically linked binary and then use our tool to monitor it.
Does this mean then that the Elemental you build is not statically linked?
Right, it is not a statically linked one.
If your Elemental is not statically linked, can you be specific about how you build Elemental, how you access and use the shared libraries it needs. I've been readng about the Elemental results you've had, but haven't looked into the details of how you build and run it.
i-static is used to statically link Intel's libraries.
MKL is linked in as .a files during the link process.
Those need to be linked in that way to succeed. I dynamically loading the Intel libraries, but that didn't work.
This builds just fine for me. Anything outside of this I haven't tried, so Xu is doing something new and the Intel compiler people might need to take a look at this combination with icpc.