> From: [email protected]
> Date: Tue, 9 Aug 2016 13:19:07 -0700
> Subject: Re: [Libmesh-users] FW: libmesh problem: libmesh_nullptr was
> not declared in scope
> To: [email protected]
> CC: marchy...@hotmail.
> From: [email protected]
> Date: Tue, 9 Aug 2016 13:33:15 -0700
> Subject: Re: [Libmesh-users] FW: libmesh problem: libmesh_nullptr was
> not declared in scope
> To: [email protected]
> CC: [email protected].
Just incase I can just have my program in with the other examples to run it
I was wondering how to view the output of the example files as well as what
line to add to the config.ac file (Under the variable AC_CONFIG_FILES) to
add a new example to libmesh.
Also I clicked reply instead of reply all
cannot remove '.libs/example-opt': Permission denied
> rm: cannot remove '.libs/lt-example-opt': Permission denied
> /usr/bin/ld: cannot open output file .libs/example-opt: Permission denied
> collect2: error: ld returned 1 exit status
>
>
>
> On Tue, Aug 9, 2016 at 10:52 AM, Mike Marchywka
The header files are in usr/local/include but they are also in
/opt/libmesh-1.0.0-rc1/include/libmesh. I think it is because the computer
I'm using has two installations of libmesh, the libmesh-1.0.0 and
libmesh-0.7.3.2. The Libmesh-1.0.0 was only recently downloaded by my
professor/PI. I obtained
n denied
> rm: cannot remove '.libs/example-opt': Permission denied
> rm: cannot remove '.libs/lt-example-opt': Permission denied
> /usr/bin/ld: cannot open output file .libs/example-opt: Permission denied
> collect2: error: ld returned 1 exit status
>
>
>
On Tue, Aug 9, 2016 at 1:54 PM, Harry Pearce
wrote:
> The program I ran wasn't in the libmesh directory when I ran it. I just
> compiled it with:
>
> mpicxx -o HPeigenproblems_PZ_8_2_16_2 HPeigenproblems_PZ_8_2_16_2.C -lz
> -Wl,-rpath,/usr/local/lib -L/usr/local/lib -lmesh_opt -I/usr/local/inclu
error: ld returned 1 exit status
On Tue, Aug 9, 2016 at 10:52 AM, Mike Marchywka
wrote:
>
>
>
>
> ________
> > From: [email protected]
> > Date: Tue, 9 Aug 2016 10:35:47 -0700
> > Subject: Re: [Libmesh-users] FW: libmesh problem:
On Tue, Aug 9, 2016 at 11:35 AM, Harry Pearce
wrote:
> Thank you for your help so far. It looks like this problem is close to
> being finished. Your recommendation of using #include "libmesh/foo.h"
> worked for compiling the program (I used the full path for
> libmesh_nullptr.h in the include par
> From: [email protected]
> Date: Tue, 9 Aug 2016 10:35:47 -0700
> Subject: Re: [Libmesh-users] FW: libmesh problem: libmesh_nullptr was
> not declared in scope
> To: [email protected]
> CC: [email protected].
> > From: [email protected]
> > Date: Mon, 8 Aug 2016 10:35:42 -0700
> > Subject: Re: [Libmesh-users] FW: libmesh problem: libmesh_nullptr was
> > not declared in scope
> > To: [email protected]; [email protected]
> > CC: libmesh-users@
> From: [email protected]
> Date: Mon, 8 Aug 2016 10:35:42 -0700
> Subject: Re: [Libmesh-users] FW: libmesh problem: libmesh_nullptr was
> not declared in scope
> To: [email protected]; [email protected]
>
rchywka
> wrote:
>
>>
>>
>>
>> Did it complain it can't find the header file first?
>> My includes for libmesh all start libmesh/foo.h
>>
>> if you run "make -n example-opt" and copy the output it should work
>> although wit
e include paths.
> From: [email protected]
> Date: Fri, 5 Aug 2016 14:07:58 -0700
> Subject: Re: [Libmesh-users] FW: libmesh problem: libmesh_nullptr was
> not declared in scope
> To: [email protected]
> CC: [email protected]; libmesh-users@lists
f_map.dof_indices (elem, dof_indices);
fe->reinit (elem);
Ke.resize (dof_indices.size(), dof_indices.size());
Me.resize (dof_indices.size(), dof_indices.size());
for (unsigned int qp=0; qpreinit (elem);
Ke.resize (dof_indices.size(), dof_indices.size());
Me
> Date: Thu, 4 Aug 2016 19:11:03 -0500
> From: [email protected]
> To: [email protected]
> CC: [email protected]
> Subject: Re: [Libmesh-users] FW: libmesh problem: libmesh_nullptr was not
> declared in sc
On Thu, 4 Aug 2016, Mike Marchywka wrote:
>> I have not followed the exchange but sometimes I end up including headers
>> within a namespace or
>> something. Is libmesh being included within something? Not sure what that
>> does with some
>> macros and others not lol.
That was my first guess,
I thought I hit "reply all"... First post to this list :)
> From: [email protected]
> To: [email protected]
> Subject: RE: [Libmesh-users] libmesh problem: libmesh_nullptr was not
> declared in scope
> Date: Thu, 4 Aug 2016 17:32:52 -0400
>
>
18 matches
Mail list logo
