<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Thanks guys...the pleasures of working with multiple architectures :-)<div><br><div><div>On Nov 4, 2010, at 10:56 AM, Jed Brown wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Thu, Nov 4, 2010 at 09:47, Bobby Philip <span dir="ltr"><<a href="mailto:philipb@ornl.gov">philipb@ornl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Is this just an extern C type issue?</blockquote></div><br><div>No, it had to do with Sun's C compiler defining __func__, but their C++ compiler does not unless you give a flag that, when set, caused an internal compiler error when building Prometheus. So I made configure test for things like __func__ separately for C and C++, but of course we can only test for the C++ version if PETSc's configure has access to a C++ compiler. I forgot to define the C++ macro when configure does not see a C++ compiler, which caused the undefined symbol when later building user code with a C++ compiler. It's fixed now.</div>
<div><br></div><div>Jed</div>
</blockquote></div><br></div></body></html>