On 1/30/13 12:01 PM, "Barrett, Brian W" <bwba...@sandia.gov> wrote:

>Actually, the errors are in code that has changed.  A couple weeks ago, we
>removed the inline assembly support for C++, but I'm guessing not entirely
>correctly.  That is, I believe something is wrong in the #defines such
>that opal_atomic_add_32 is being declared inline, but no inline body will
>be provided, so it all falls down.  Siegmar, can you send me your
>opal/include/opal_config.h file when running with the Studio compilers?  I
>don't have then available on x86 and it's probably faster for you to send
>me the files than for me to try to setup a Linux box with the compilers
>installed.

Siegmar -

Can you try the attached patch and see if it fixes the compile error
you're seeing?  I think I found the issue.

Thanks,

Brian

--
  Brian W. Barrett
  Scalable System Software Group
  Sandia National Laboratories




Attachment: atomic.diff
Description: Binary data

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to