> This line of code has been in the library forever and never given us
> any trouble, but now that I look at it closely I'm not sure you are
> allowed to compare two streams for equality like this.  Can you try
> changing that line of code to:
> 
> if (os.rdbuf() == std::cout.rdbuf())
> 
> instead, and see if your compiler likes that any better?

Yes! This did the trick! I have now managed to compile and run the tests and 
everything seems to be fine now. Thank you very much for your assistance. 

Incidentally, my earlier problem with getting the configure stage to recognise 
vtk was due to having misspelt the location of the directory where vtk-related 
libraries reside, so that is solved as well. 

Best wishes,

Eduardo

Eduardo R. Hernández
Instituto de Ciencia de Materiales de Madrid (ICMM)
Consejo Superior de Investigaciones Científicas
Campus de Cantoblanco
28049 Madrid

tel.: +34 91 3348994
email: [email protected]
http://www.icmm.csic.es/ehernandez/Site/Home.html



On 12 Sep 2014, at 07:32, John Peterson <[email protected]> wrote:

> On Thu, Sep 11, 2014 at 8:57 AM, Eduardo Hernandez
> <[email protected]> wrote:
>> 
>> 
>> Hello John,
>> 
>> Thank you for your speedy response. I did as you suggested and downloaded 
>> the latest development version; sadly it still fails at the make stage, but 
>> this time with a different error, still apparently related to talking with 
>> petsc...
>> 
>>  CXX      src/numerics/libmesh_dbg_la-petsc_matrix.lo
>> src/numerics/petsc_matrix.C:599:10: error: invalid operands to binary 
>> expression ('std::ostream'
>>      (aka 'basic_ostream<char>') and 'ostream' (aka 'basic_ostream<char>'))
>>  if (os == std::cout)
>>      ~~ ^  ~~~~~~~~~
>> 1 error generated.
>> 
>> Any further hints?
> 
> 
> This line of code has been in the library forever and never given us
> any trouble, but now that I look at it closely I'm not sure you are
> allowed to compare two streams for equality like this.  Can you try
> changing that line of code to:
> 
> if (os.rdbuf() == std::cout.rdbuf())
> 
> instead, and see if your compiler likes that any better?
> 
> http://stackoverflow.com/questions/3318714/check-if-ostream-object-is-cout-or-ofstream-c
> 
> -- 
> John

------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users

Reply via email to