Again, if I build the library with "dbg" option. Here are the messages:
*./include/libmesh/ostream_proxy.h:116:16: **error: **call to function
'operator<<' that is neither visible in*
* the template definition nor found by argument-dependent lookup*
(*_target) << in;
* ^*
*src/mesh/mesh_communication_global_indices.C:400:15: note: *in
instantiation of function template
specialization 'libMesh::BasicOStreamProxy<char,
std::__1::char_traits<char>
>::operator<<<std::__1::pair<Hilbert::HilbertIndices, unsigned long
long> >' requested here
libmesh_assert_less_equal (hi,
node_upper_bounds[communicator.rank()]);
* ^*
*./include/libmesh/libmesh_common.h:345:48: note: *expanded from macro
'libmesh_assert_less_equal'
#define libmesh_assert_less_equal(expr1,expr2)
libmesh_assert_less_equal_msg(expr1,expr2, "")
* ^*
*./include/libmesh/libmesh_common.h:326:85: note: *expanded from macro
'libmesh_assert_less_equal_msg'
libMesh::err << "Assertion `" #expr1 " <= " #expr2 "' failed.\n"
#expr1 " = " << (expr1) << "\n" #e...
*
^*
*./include/libmesh/parallel_hilbert.h:84:1: note: *'operator<<' should be
declared prior to the call site or
in namespace 'Hilbert'
operator <<
*^*
1 error generated.
make[1]: *** [src/mesh/libmesh_dbg_la-mesh_communication_global_indices.lo]
Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [all-recursive] Error 1
On Thu, Jan 7, 2016 at 10:13 PM, Xujun Zhao <xzha...@gmail.com> wrote:
> I updated my Xcode and Command Line Tools by mistake. This is boring every
> time. Now I have turned the autocheck off.
> I am not sure if there is the same problem on other Macbooks, it is
> probably difficult to persuade people around me to upgrade, especially if
> they can see this post :-)
>
>
>
> On Thu, Jan 7, 2016 at 10:02 PM, John Peterson <jwpeter...@gmail.com>
> wrote:
>
>>
>>
>> > On Jan 7, 2016, at 8:21 PM, Roy Stogner <royst...@ices.utexas.edu>
>> wrote:
>> >
>> >
>> >> 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.
>>
>> It's working fine for me, but I have not upgraded to the latest Xcode and
>> we use a clang 3.7.0 compiler built from source.
>>
>>
>>
>
------------------------------------------------------------------------------
_______________________________________________
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users
