Thank you for your response.

I checked the code of the file I am compiling and it doesn't reference an
libmesh_nullptr variables. I also commented out the #include
"libmesh_nullptr.h" in my file and it didn't change the nature of the
errors at all. The compiler complains about libmesh_nullptr through
mesh_generation.h and equation_systems.h.

I noticed that the only lines of my original code the compiler mentions as
sources of error are just places in my code where I added #include
"someheaderhere"

An example error of this type is:
In file included from HPeigenproblems_PZ_8_2_16_2.C:4:0:
/opt/libmesh-1.0.0-rc1/include/libmesh/mesh_generation.h:130:67: error:
‘libmesh_nullptr’ was not declared in this scope
                       QueryElemSubdomainIDBase * elem_subdomain =
libmesh_nullptr);

Notice that the error is in the file included from line 4 of my code. All
line 4 of my code says is #include "mesh_generation.h"
The compiler is only finding problems with the lines #include
"mesh_generation.h",  #include "equation_systems.h", and #include
"sparse_matrix.h.h"

Originally this example code was made using an earlier version of libmesh.
I didn't modify it except for adding headers that I thought might help (I
recently added #include "libmesh_nullptr.h" to it to see if it would fix
the libmesh_nullptr problem, but it didn't so I commented it out).

I also tried commenting out the #include files that the had errors but this
resulted in other errors due to those header files being necessary for the
program

Could the problem be how things are being compiled or the way my header
files are setup?

Harry Pearce

On Thu, Aug 4, 2016 at 11:05 AM, Harry Pearce <[email protected]>
wrote:

> Thank you for your response.
>
>
> I checked the code of the file I am compiling and it doesn't reference an
> libmesh_nullptr variables. I also commented out the #include
> "libmesh_nullptr.h" in my file and it didn't change the nature of the
> errors at all. The compiler complains about libmesh_nullptr through
> mesh_generation.h and equation_systems.h.
>
> I noticed that the only lines of my original code the compiler mentions as
> sources of error are just places in my code where I added #include
> "someheaderhere"
>
> An example error of this type is:
> In file included from HPeigenproblems_PZ_8_2_16_2.C:4:0:
> /opt/libmesh-1.0.0-rc1/include/libmesh/mesh_generation.h:130:67: error:
> ‘libmesh_nullptr’ was not declared in this scope
>                        QueryElemSubdomainIDBase * elem_subdomain =
> libmesh_nullptr);
>
> Notice that the error is in the file included from line 4 of my code. All
> line 4 of my code says is #include "mesh_generation.h"
> The compiler is only finding problems with the lines #include
> "mesh_generation.h",  #include "equation_systems.h", and #include
> "sparse_matrix.h.h"
>
> Originally this example code was made using an earlier version of libmesh.
> I didn't modify it except for adding headers that I thought might help (I
> recently added #include "libmesh_nullptr.h" to it to see if it would fix
> the libmesh_nullptr problem, but it didn't so I commented it out).
>
> I also tried commenting out the #include files that the had errors but
> this resulted in other errors due to those header files being necessary for
> the program.
>
> Harry Pearce
>
> On Thu, Aug 4, 2016 at 9:35 AM, John Peterson <[email protected]>
> wrote:
>
>>
>>
>> On Thu, Aug 4, 2016 at 10:25 AM, Harry Pearce <[email protected]>
>> wrote:
>>
>>> Hello libmesh users,
>>> I am trying to compile a modified libmesh example program but I keep
>>> getting the error " 'libmesh_nullptr' was not declared in this scope."
>>>
>>>  I am already using the libmesh namespace and obtained my compile command
>>> using:
>>> echo  `libmesh-config --cxx` -o `libmesh-config --cxxflags --include
>>> --ldflags --libs`
>>>
>>> I am compiling with mpicxx.
>>>
>>> If it helps I can provide the example code I'm using and/or the errors.
>>> I'm
>>> using libmesh version 1.0.0.
>>>
>>
>> I still don't see how this is possible, but if this is really the only
>> issue you have, why don't you just change libmesh_nullptr in your code to
>> NULL?
>>
>
>
------------------------------------------------------------------------------
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users

Reply via email to