Thank you!
I included the -n , number of eigenvalues, and a name and now the program
runs!
Harry Pearce
On Thu, Aug 18, 2016 at 11:15 AM, John Peterson
wrote:
>
>
> On Thu, Aug 18, 2016 at 10:49 AM, Harry Pearce
> wrote:
>
>> Including "libmesh/node.h" got rid of the error when using make
>> e
On Thu, Aug 18, 2016 at 10:49 AM, Harry Pearce
wrote:
> Including "libmesh/node.h" got rid of the error when using make
> example-opt for my modified example. I was wondering what I do to view the
> output of the C program though. I would think I should run example-opt.
> When I did this I got th
Including "libmesh/node.h" got rid of the error when using make example-opt
for my modified example. I was wondering what I do to view the output of
the C program though. I would think I should run example-opt. When I did
this I got the output:
Usage: /opt/libmesh-1.0.0-rc1/examples/eigenproblems/
On Wed, Aug 17, 2016 at 4:05 PM, Harry Pearce
wrote:
> I updated the .C program based on the up to date examples. The only error I
> get now is:
> CXX example_opt-eigenproblems_ex2.o
> eigenproblems_ex2.C: In function ‘int main(int, char**)’:
> eigenproblems_ex2.C:89:32: error: invalid ini
> From: harroontheg...@gmail.com
> Date: Wed, 17 Aug 2016 15:05:13 -0700
> Subject: Re: [Libmesh-users] Example files won't run a second time
> To: codyperm...@gmail.com
> CC: marchy...@hotmail.com; libmesh-users@lists.sourceforge.net
&
t; >> directory but doesn't do anything other than "make all-am". Then it says
> >> there is nothing to do in the directory of the example and looks at the
> >> next example.
> >>
> >> Harry Pearce
> >>
> >> On Fri, Aug 12, 2016
gt;> > Silent failures can be hard to track down. Normally, you could just
>> > start in a debugger. Or, if you think you are missing a library
>> > run ldd. It turns out the output of the libtool step is a script
>> > that runs .libs/lt-foo. and you can run ldd on this if you
> From: codyperm...@gmail.com
> Date: Tue, 16 Aug 2016 19:37:52 +
> Subject: Re: [Libmesh-users] Example files won't run a second time
> To: harroontheg...@gmail.com; marchy...@hotmail.com
> CC: libmesh-users@lists.sourceforge.net
&g
I usually just write a script that rebuilds
> > everything although checking for "newer" would not be too hard.
> >
> > Again, the compile seems normal but maybe someone could explain the
> > odd linking lol. What is the point of this?
> >
> > When I g
> From: harroontheg...@gmail.com
> Date: Tue, 16 Aug 2016 11:19:13 -0700
> Subject: Re: [Libmesh-users] Example files won't run a second time
> To: marchy...@hotmail.com
> CC: libmesh-users@lists.sourceforge.net
>
>>Again, I
hich uses tcl and things like jdft.
> I have no idea how this will go but curious what you find :)
>
>
>
>
>
>
>
> > From: harroontheg...@gmail.com
> > Date: Fri, 12 Aug 2016 12:34:41 -0700
> > To: libmesh-users@li
On Fri, 12 Aug 2016, Mike Marchywka wrote:
> Again, the compile seems normal but maybe someone could explain the
> odd linking lol. What is the point of this?
Originally, the point of running libtool was that it allowed the same
build system to support all the weird options for static and dynami
g 2016 12:34:41 -0700
> To: libmesh-users@lists.sourceforge.net
> Subject: [Libmesh-users] Example files won't run a second time
>
> Hello libmesh users!,
> I tried to run the example programs using make run_examples but after the
> makefile descends into the individual example fi
Hello libmesh users!,
I tried to run the example programs using make run_examples but after the
makefile descends into the individual example files it keeps saying
"Nothing to be done for all-am" after trying to make all-am. It doesn't try
to run or modify the programs. I wanted to recompile the ei
14 matches
Mail list logo
