I have the --disable-unique-ptr option in my configuration script since it is
required by another library I’m using on top of libMesh.
Thanks,
Simone
On Nov 7, 2016, at 11:49, John Peterson
mailto:jwpeter...@gmail.com>> wrote:
On Mon, Nov 7, 2016 at 9:28 AM, Rossi, Simone
mailto:sro...@ema
On Mon, 7 Nov 2016, John Peterson wrote:
With this change it compiles fine, but I since ’m not using the rb classes
and I cannot say if this is the best way to solve this problem.
Thanks, the fix looks OK to me, but I'm wondering how you ended up with a
libMesh::AutoPtr here. Did you explic
On Mon, Nov 7, 2016 at 9:28 AM, Rossi, Simone wrote:
> Dear all,
> I’m upgrading to PETSc 3.7.4 and I am now compiling the git version of
> libMesh.
> On my workstation (using gcc 5.4 and openmpi 2.0.0) I get a compilation
> error
>
> /not_backed_up/srossi/TPL/libmesh/libmesh-git/src/
> reduced_b
On Mon, 7 Nov 2016, Rossi, Simone wrote:
I solved the error just by changing
if (_qrule != libmesh_nullptr) =>if (_qrule.get() != libmesh_nullptr)
With this change it compiles fine, but I since ’m not using the rb classes and
I cannot say if this is the best way to solve this problem
Dear all,
I’m upgrading to PETSc 3.7.4 and I am now compiling the git version of libMesh.
On my workstation (using gcc 5.4 and openmpi 2.0.0) I get a compilation error
/not_backed_up/srossi/TPL/libmesh/libmesh-git/src/reduced_basis/rb_eim_assembly.C:
In member function ‘virtual void
libMesh::RB
> On Oct 3, 2014, at 11:57 AM, Roy Stogner wrote:
>
>
>
> On Fri, 3 Oct 2014, John Peterson wrote:
>
>>> libtool makes you jump through a bunch of annoying scripts, and
>>> unless you need help making your stuff compile on 1990s Unices, the
>>> only benefit is that it gets your dependency li
On Fri, 3 Oct 2014, John Peterson wrote:
>> libtool makes you jump through a bunch of annoying scripts, and
>> unless you need help making your stuff compile on 1990s Unices, the
>> only benefit is that it gets your dependency library flags right.
>> You had ONE JOB to do, libtool!
>
> I don't k
> On Oct 3, 2014, at 11:51 AM, Roy Stogner wrote:
>
>
>> On Fri, 3 Oct 2014, Dana Christen wrote:
>>
>> That's interesting: link_all_deplibs is set to "no" on this Ubuntu
>> 14.04 machine. However, it is set to "unknown" on a machine running
>> Ubuntu 13.04, where everything works fine.
>
>
On Fri, 3 Oct 2014, Dana Christen wrote:
> That's interesting: link_all_deplibs is set to "no" on this Ubuntu
> 14.04 machine. However, it is set to "unknown" on a machine running
> Ubuntu 13.04, where everything works fine.
This might be it, then. While looking through some unrelated code
hist
That's interesting: link_all_deplibs is set to "no" on this Ubuntu 14.04
machine. However, it is set to "unknown" on a machine running Ubuntu 13.04,
where everything works fine.
FYI, uninstalling the system netcdf and starting from a fresh clone didn't
work, but Miguel's workaround did.
Dana
On
Hey, here's a question - what does link_all_deplibs get set to in your
./libtool script? Debian+Ubuntu disable that, but we depend on it. I
*thought* that our practice of distributing the output of bootstrap
was enough to avoid requiring deb users to build their own autotools,
but perhaps that'
Hi Roy,
Thanks for your reply. Uninstalling the system netcdf doesn't help. Running
make -n shows that the problematic command is the following:
/bin/bash ./libtool --silent --tag=CXX --mode=link mpicxx -std=gnu++11
-O2 -felide-constructors -funroll-loops -fstrict-aliasing
-Wdisabled-optimizati
On Fri, 3 Oct 2014, Dana Christen wrote:
> Just realized there was a typo in my original message: I updated to Ubuntu
> 14.04 (latest long-term-support version). This error occurs with GCC 4.7.3,
> GCC 4.8.2, with and without the system netcdf libraries.
You're not the first person to run into t
Just realized there was a typo in my original message: I updated to Ubuntu
14.04 (latest long-term-support version). This error occurs with GCC 4.7.3,
GCC 4.8.2, with and without the system netcdf libraries.
Thanks,
Dana
On Fri, Oct 3, 2014 at 12:15 PM, Dana Christen
wrote:
> Hello,
>
> I updat
Hello,
I updated my workstation to Ubuntu 10.04 and libMesh now fails to compile.
I'm getting the following error while compiling the latest revision of a
fresh libmesh clone:
(...)
CXXLDmeshid-opt
/usr/bin/ld: src/apps/meshid_opt-meshid.o: undefined reference to symbol
'nc_close'
//mnt/DATA/
Oh, yeah, that looks good, thanks.
This didn't cause any compilation problem for me, not sure why...
David
On 12/06/2013 01:08 PM, Manav Bhatia wrote:
> I ended up adding the a call to the mesh constructor in the RBEIMEvaluation
> constructor with “comm” as the argument.
>
> Not sure if this
I ended up adding the a call to the mesh constructor in the RBEIMEvaluation
constructor with “comm” as the argument.
Not sure if this would be the correct communicator to pass. Maybe David could
comment.
-Manav
RBEIMEvaluation::RBEIMEvaluation(const libMesh::Parallel::Communicator &comm)
On Fri, Dec 6, 2013 at 10:03 AM, Manav Bhatia wrote:
> Hi,
>
> I got the latest libMesh from github, and compilation on Mac OS X with
> clang5 gives the following error:
>
> src/reduced_basis/rb_eim_evaluation.C:37:20: error: constructor for
> 'libMesh::RBEIMEvaluation' must explicitly initiali
Hi,
I got the latest libMesh from github, and compilation on Mac OS X with clang5
gives the following error:
src/reduced_basis/rb_eim_evaluation.C:37:20: error: constructor for
'libMesh::RBEIMEvaluation' must explicitly initialize the member
'_interpolation_points_mesh' which does not have
I have compiled and installed libmesh; when I try to make an example program
using Makefile.old I get the following error:
Makefile:68: .depend: No such file or directory
Compiling C++ (in optimized mode) introduction_ex2.C...
Linking introduction_ex2-opt...
ld: warning: ignoring file introducti
-Original Message-
From: Cody Permann
To: "Welland, Michael Joshua"
Cc: "Paul T. Bauman" ,
"libmesh-users@lists.sourceforge.net"
Subject: Re: [Libmesh-users] Compilation error when compiling Libmesh
>Sent from my evil iPhone
>
>On Jul 27, 2012, at 4:33 PM, &
l T. Bauman" mailto:ptbau...@gmail.com>>,
> "libmesh-users@lists.sourceforge.net<mailto:libmesh-users@lists.sourceforge.net>"
>
> mailto:libmesh-users@lists.sourceforge.net>>
> Subject: Re: [Libmesh-users] Compilation error when compiling Libmesh
&g
orge.net<mailto:libmesh-users@lists.sourceforge.net><mailto:libmesh-users@lists.sourceforge.net<mailto:libmesh-users@lists.sourceforge.net>>"
mailto:libmesh-users@lists.sourceforge.net><mailto:libmesh-users@lists.sourceforge.net<mailto:libmesh-users@lists.sourcefo
; From: "Paul T. Bauman" mailto:ptbau...@gmail.com>>
> To: "Welland, Michael Joshua" mailto:mwell...@anl.gov>>
> Cc: "libmesh-users@lists.sourceforge.net libmesh-users@lists.sourceforge.net>" <mailto:libmesh-users@lists.sourceforge.net>>
> Subject:
ael Joshua" mailto:mwell...@anl.gov>>
Cc:
"libmesh-users@lists.sourceforge.net<mailto:libmesh-users@lists.sourceforge.net>"
mailto:libmesh-users@lists.sourceforge.net>>
Subject: Re: [Libmesh-users] Compilation error when compiling Libmesh
On Fri, Jul 27, 2012 at 2
On Fri, Jul 27, 2012 at 2:01 PM, Welland, Michael J. wrote:
> Hi all, I'm having a problem compiling libmesh on my Mac (version 10.7.4)
>
> When it gets to "Building Contributed Packages" it stops after:
>
> Compiling C++ (in optimized mode) util/cpp_compress_main.cc...
> Linking (in optimized mo
Hi all, I'm having a problem compiling libmesh on my Mac (version 10.7.4)
When it gets to "Building Contributed Packages" it stops after:
Compiling C++ (in optimized mode) util/cpp_compress_main.cc...
Linking (in optimized mode) util/cpp_compress.x86_64-apple-darwin11.4.0.opt.o...
Creating Bytec
fixes it, thanks!
On 11/01/2011 03:25 PM, John Peterson wrote:
> On Tue, Nov 1, 2011 at 1:20 PM, David Knezevic
> wrote:
>> I just svn up'd and ./configure'd and I'm getting the compilation error:
>>
>> Compiling C++ (in debug mode) src/base/dof_map.C...
>> In file included from
>> /home/dkne
On Tue, Nov 1, 2011 at 1:20 PM, David Knezevic
wrote:
> I just svn up'd and ./configure'd and I'm getting the compilation error:
>
> Compiling C++ (in debug mode) src/base/dof_map.C...
> In file included from
> /home/dknez/software/libmesh/include/base/dof_map.h:39:0,
> from src/base/dof_map.C:30:
I just svn up'd and ./configure'd and I'm getting the compilation error:
Compiling C++ (in debug mode) src/base/dof_map.C...
In file included from
/home/dknez/software/libmesh/include/base/dof_map.h:39:0,
from src/base/dof_map.C:30:
/home/dknez/software/libmesh/include/parallel/threads_allocators
On Tue, Sep 1, 2009 at 9:06 AM, zeljka wrote:
> Hi there!
> I am tying to compile the svn version but the following errors occur
>
> In file included from src/numerics/eigen_solver.C:27:
> /home/zeljka/libmesh/include/numerics/eigen_solver.h:200: error:
> expected unqualified-id before ‘<<’ token
>
Hi there!
I am tying to compile the svn version but the following errors occur
In file included from src/numerics/eigen_solver.C:27:
/home/zeljka/libmesh/include/numerics/eigen_solver.h:200: error:
expected unqualified-id before ‘<<’ token
/home/zeljka/libmesh/include/numerics/eigen_solver.h:208:
Charuka Jayarathna wrote:
> Hello,
>
> I tried to compile with gmake.
> and got the following error.
>
> src/mesh/xdr_io.C: In member function `virtual void XdrIO::write(const
>std::string&)':
> src/mesh/xdr_io.C:150: error: parse error before `,' token
> src/mesh/xdr_io.C:152: confused by ea
On Fri, 16 Jan 2009, Charuka Jayarathna wrote:
> I am trying to compile libmesh on a system IRIX64 hydra 6.5 07202013 IP2.
>
> I am getting following error
>
> 5% make
> make: file `Make.common' line 42: Must be a separator (: or ::) for rules
> (bu39)
Make.common differs from system to system
Hello,
I am trying to compile libmesh on a system IRIX64 hydra 6.5 07202013 IP2.
I am getting following error
5% make
make: file `Make.common' line 42: Must be a separator (: or ::) for rules (bu39)
make: file `Make.common' line 42: Must be a separator (: or ::) for rules (bu39)
make: file `M
On Thu, 15 Jan 2009, Mengda Wu wrote:
> I am using the version 10.1.008 on a 64bit linux platform.
Odd. Both 10.1.017 and the old 7.0 I had lying around worked.
> Your solution does fix the problem for that file, but the same error comes
> out for other files:
Yeah; I did some refactoring and
I am using the version 10.1.008 on a 64bit linux platform.
Your solution does fix the problem for that file, but the same error comes
out for other files:
Compiling C++ (in optimized mode) src/numerics/petsc_nonlinear_solver.C...
src/numerics/petsc_nonlinear_solver.C(90): error: more than one ins
On Thu, 15 Jan 2009, Mengda Wu wrote:
> I used intel compiler to build the latest svn version of libmesh.
Which version? It compiled fine with icc 10.1.017 for me, but if I've
just inadvertantly broken older Intel compilers I'd definitely like to
fix that.
> I got the following error in th
Hi all,
I used intel compiler to build the latest svn version of libmesh. I got
the following error in the middle.
Compiling C++ (in optimized mode) src/numerics/mesh_function.C...
src/numerics/mesh_function.C(116): error: more than one instance of
overloaded function "libmesh_assert_cast"
39 matches
Mail list logo
