On Fri, 8 Jan 2016, Roy Stogner wrote:
> Let me try putting that overload into Hilbert instead of libMesh and
> see if it works for me. If it does then I'll upload a pull request
> and we can see if it works for you too.
It does work for me. See if
https://github.com/libMesh/libmesh/pull/771
On Fri, 8 Jan 2016, Xujun Zhao wrote:
Again, if I build the library with "dbg" option. Here are the messages:
This is extremely helpful, thanks!
./include/libmesh/parallel_hilbert.h:84:1: note: 'operator<<' should be
declared prior to the call site or
in namespace 'Hilbert'
It loo
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;
* ^*
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, J
> On Jan 7, 2016, at 8:21 PM, Roy Stogner 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 simi
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 ostr
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 instal
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 t
On Thu, 7 Jan 2016, John Peterson wrote:
> Hmm... the error seems to be triggered by this line of code:
>
> libMesh::err << "node " << (*nodej)->id() << ", " <<
>*(Point *)(*nodej) << " has HilbertIndices " <<
>node_keys[j] << std::endl;
>
On Thu, 7 Jan 2016, Xujun Zhao wrote:
> If I go the file and comment the line (*_target) << in;
> it can pass the compilation on my Mac
You definitely *don't* want to comment out that line; that would
disable most libMesh stdout/stderr messages.
You could, however, comment out just the HilbertI
On Thu, Jan 7, 2016 at 3:20 PM, Xujun Zhao wrote:
> Hi all,
>
> I am reporting a compiling error with Xcode command line tools version 7.2
> Apple LLVM version 7.0.2 (clang-700.1.81)
>
> The configure log file is attached, and the error messages are as follows.
> If I go the file and comment the
Hi all,
I am reporting a compiling error with Xcode command line tools version 7.2
Apple LLVM version 7.0.2 (clang-700.1.81)
The configure log file is attached, and the error messages are as follows.
If I go the file and comment the line (*_target) << in;
it can pass the compilation on my Mac
--
12 matches
Mail list logo
