On Thu, 7 Jan 2016, Xujun Zhao wrote:

I did try to comment on line 615-618 in mesh_communication_global_indices.C. However, 
other lines which have libMesh::err <<, for example, line
620-623, line 649-655 ..., led to the similar error messages. That is why I 
comment on that single line in ostream_proxy.h. 

Yeah; there ought to be operator<<(pair<Hilbert,unique>) usage
throughout that file.

After installation, I also change it back and uncommented on this line in the 
installed files. Then libMesh::err << can still work in my code.
However, I am not sure if the stdout/stderr functions in libMesh functions are 
disabled, because the operator << is only defined in the header
file.

That's grotesque but clever.  Yeah, that should disable output from
the library itself but still leave output from your application code
working.

BTW, I use the most recent version of libMesh, which was pulled from
master branch this afternoon.

Thanks.

Are there any other OSX users who can replicate this?  I don't think I
have easy access to any Macs right now.
---
Roy
------------------------------------------------------------------------------
_______________________________________________
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users

Reply via email to