Hi John and Roy, 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.
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. BTW, I use the most recent version of libMesh, which was pulled from master branch this afternoon. Best, Xujun On Thu, Jan 7, 2016 at 6:15 PM, Roy Stogner <royst...@ices.utexas.edu> wrote: > > On Thu, 7 Jan 2016, Roy Stogner wrote: > > If you want to help us replicate/fix the problem then we need to know >> what version (release number if you're using a tarball, or git hash >> otherwise) of libMesh you're using. >> > > Never mind this; from context it's obvious that you've found a problem > with the HEAD on master. > --- > Roy > ------------------------------------------------------------------------------ _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
