John Peterson,
Thanks. I tried it with ./configure and it didn't work either but I will
ask the SLEPc developers about it.
Thankfully,
Harry Pearce
On Fri, Oct 19, 2018 at 12:27 PM John Peterson wrote:
>
>
> On Fri, Oct 19, 2018 at 1:03 PM Harry Pearce
> wrote:
>
>&
Libmesh Users,
I am having trouble with getting slepc to read my PETSC_DIR environment
variable.
I successfully installed PETSC and set the environment variable for
PETSC_DIR in my .bashrc file. When I try execute the following slepc
configure script this is what happens:
*hpearce@tcol:/islhome/h
c and
slepc directories, but I fixed the bashrc file and this error still
persists. A new config.log file is attached.
Harrison Pearce
SDSU Undergraduate in Chemical Physics
On Wed, Aug 1, 2018 at 3:28 PM, Harry Pearce
wrote:
> Paul,
> Here it is! There is another problem but I think I
Paul,
Here it is! There is another problem but I think I know what's causing it
so I will ask if I can't figure it out.
Thanks again,
Harrison Pearce
SDSU undergraduate in Chemical Physics
On Wed, Aug 1, 2018 at 3:10 PM, Paul T. Bauman wrote:
>
>
> On Wed, Aug 1, 2018 at 5
mailing
> list will strip it).
> I'm curious to see what caused that failure.
>
> On Wed, Aug 1, 2018 at 4:17 PM Harry Pearce
> wrote:
>
>> Hello fellow libmesh users!,
>>
>> I am trying to configure libmesh 1.3.0.
>> When I run ./configure I get the e
Hello fellow libmesh users!,
I am trying to configure libmesh 1.3.0.
When I run ./configure I get the error:
checking for Boost headers version >= 1.47.0... yes
checking for Boost's header version... 1_55
checking for the toolset name used by Boost for mpicxx... configure:
WARNING: could not figur
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 r
)
[0x40c17e]
3: __libc_start_main
4:
/opt/libmesh-1.0.0-rc1/examples/eigenproblems/eigenproblems_ex2/.libs/lt-example-opt()
[0x40c29d]
[0] eigenproblems_ex2.C, line 45, compiled Aug 17 2016 at 15:52:06
application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0
Harry Pearce
On Wed, Aug 17, 2016 at 3:47 PM,
from expression of type ‘libMesh::Node’
const Point& p = **node_it;
^
This looks like a C++ error to me but supposedly the code used to work. Was
libmesh::Point a class in the old libMesh (libMesh 0.7.3.3)?
Thankfully,
Harry Pearce
On Tue, Aug 16, 20
2.o] Error 1
Also I ran make check and the examples do rerun when I do that but now when
I do make run_examples. When I do make run_examples it looks in each
directory but doesn't do anything other than "make all-am". Then it says
there is nothing to do in the directory of the
Professor never used make check when downloading libmesh-1.0.0-rc1.
Instead he used make run_examples.
Does anyone know why the example programs aren't running (they ran the
first time) and how to fix it?
Thankfully,
Harry Pearce
---
e name collision.
Harry Pearce
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Pr
o I moved my .C file in and got a
different series of errors.
On Tue, Aug 9, 2016 at 12: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_
ained the compile line by typing in:
`libmesh-config --cxx` -o foo foo.C `libmesh-config --cxxflags
--include --ldflags --libs` which I found out about from the
libmesh website section "installation".
On Tue, Aug 9, 2016 at 1:00 PM, John Peterson wrote:
>
>
> On Tue, Aug 9
don't need them in the directory would that mean that I could make
them in a directory other than the example directory?
On Tue, Aug 9, 2016 at 12:54 PM, Harry Pearce
wrote:
>
> The program I ran wasn't in the libmesh directory when I ran it. I just
> compiled
lthough make clean may help first.
>
> And again go to the examples and run make -n on any target and
> see what you get.
>
> Curious what the name collision is however. I just ran a script to find
> repeated names in my /usr/include and some occur 30 times lol.
> Using directories is
ould think linking would work just as well as adding to my example
programs so I added -L/opt/slepc-3.7.0/sys
to the compiling command but this didn't fix the problem.
Harry Pearce
On Mon, Aug 8, 2016 at 11:20 AM, Mike Marchywka
wrote:
>
>
>
>
>
make[1]: Entering directory `/opt/libmesh-1.0.0-rc1/examples/eigenproblems/
eigenproblems_femviblibtests_ex1'
make[1]: *** No rule to make target `all'. Stop.
make[1]: Leaving directory `/opt/libmesh-1.0.0-rc1/examples/eigenproblems/
eigenproblems_femviblibtests_ex1'
make: *** [all-recur
but I do not see
the directories of any other example programs in AC_CONFIG_FILES within the
configure.ac program.
Harry Pearce
Just in case highlighting doesn't show up on the libmesh users archive, the
highlighted code is below:
#include
#include "libmesh.h"
#include
Does this mean the something is likely to have gone wrong with the
installation of libmesh?
Harry Pearce
On Thu, Aug 4, 2016 at 12:48 PM, Roy Stogner
wrote:
>
> On Thu, 4 Aug 2016, Harry Pearce wrote:
>
> In regards to LIBMESH_HAVE_CXX11_NULLPTR it says:
&
Yes it does have /* #undef HAVE_CXX11_NULLPTR_BUT_DISABLED */
Harry Pearce
On Thu, Aug 4, 2016 at 1:56 PM, Roy Stogner
wrote:
>
> On Thu, 4 Aug 2016, Harry Pearce wrote:
>
> "/* Compiler supports nullptr, but it is disabled in libmesh */"
>>
>
> means th
Could it be the case that
"/* Compiler supports nullptr, but it is disabled in libmesh */"
means that libmesh can't use nullptr since it's disabled in libmesh,
meaning that #define libmesh_nullptr can't be defined nullptr, because
nullptr is disabled?
Harry Pearce
On Th
ed in libmesh */
/* #undef HAVE_CXX11_NULLPTR_BUT_DISABLED */
/* Flag indicating whether C++03 compatible nullptr workaround works */
/* #undef HAVE_CXX11_NULLPTR_WORKAROUND */
/* Flag indicating whether compiler supports the override keyword */
Harry Pearce
On Thu, Aug 4, 2016 at 11:31 AM
ither it is a compiling error or equation_systems.h needs to be modified
in some way to work, do you have any other ideas of what the problem might
be?
Harry Pearce
On Thu, Aug 4, 2016 at 11:06 AM, Harry Pearce
wrote:
> Thank you for your response.
>
>
> I checked the code of the fi
e #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
wrote:
> Th
` -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.
name a type
static UniquePtr >
If it helps I can provide the example code I'm using. I'm using libmesh
version 1.0.0.
Harry Pearce
On Wed, Aug 3, 2016 at 1:12 PM, John Peterson wrote:
>
>
> On Wed, Aug 3, 2016 at 2:06 PM, Harry Pearce
> wrote:
>
>&
e a compiler issue? I am using mpicxx to compile.
Harry Pearce
--
___
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users
from HPeigenproblems_PZ_8_2_16_2.C:2:
/usr/local/include/libmesh/parallel.h:328:37: error:"
Does this make a difference?
Inquisitively,
Harry Pearce
On Wed, Aug 3, 2016 at 11:27 AM, John Peterson wrote:
>
>
> On Wed, Aug 3, 2016 at 12:22 PM, Harry Pearce
> wrote:
>
>> Hel
with parallel.h is fixed.
Thank you for reading this,
Harry Pearce
--
___
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users
30 matches
Mail list logo
