Hello,
yes that works. But I have discovered some other issues:
- The installed libmesh-config script does not work, if it is called using
a relative file path. Removing "$script_path" from line 37 fixes this.
- In my opinion the installed stuff should follow somehow the FHS, so
there are no probl
On Nov 20, 2012, at 10:04 AM, Robert wrote:
> Hello,
>
> yes that works. But I have discovered some other issues:
> - The installed libmesh-config script does not work, if it is called using
> a relative file path. Removing "$script_path" from line 37 fixes this.
> - In my opinion the installe
On Mon, Nov 19, 2012 at 1:56 PM, Kirk, Benjamin (JSC-EG311)
wrote:
> My feeling is installing them with a couple line makefile would be better -
>
> $ cp -r /libmesh/example ./myexample
>
> make & play
>
> encourages more learning anyway.
Yeah, I agree we don't really need the binaries but the in
On Nov 20, 2012, at 3:06 PM, John Peterson wrote:
> On Mon, Nov 19, 2012 at 1:56 PM, Kirk, Benjamin (JSC-EG311)
> wrote:
>> My feeling is installing them with a couple line makefile would be better -
>>
>> $ cp -r /libmesh/example ./myexample
>>
>> make & play
>>
>> encourages more learning
Hey,
Realize that there have been some discussions on this and this was
supposed to be resolved, but I am getting the following error after I just
svn upped.
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash
/home/vikramvg/libmesh/build-aux/missing --run aclocal-1.12 -I m4
/home/vikramvg/libm
> Hey,
>Realize that there have been some discussions on this and this was
> supposed to be resolved, but I am getting the following error after I just
> svn upped.
Not resolved satisfactorily yet. Try
$ svn revert * m4/* build-aux/*
$ ./bootstrap
to rebuild the build system with you
That seems to work, almost. I am getting some errors regarding some local
files that I had added,
CXXLD meshtool
./.libs/libmesh.so: undefined reference to `vtable for
libMesh::NoSolutionHistory'
collect2: ld returned 1 exit status
make[1]: *** [meshtool] Error 1
make[1]: Leaving directory `/hom
On Nov 20, 2012, at 4:10 PM, Vikram Garg wrote:
> That seems to work, almost. I am getting some errors regarding some local
> files that I had added,
>
> CXXLD meshtool
> ./.libs/libmesh.so: undefined reference to `vtable for
> libMesh::NoSolutionHistory'
> collect2: ld returned 1 exit statu
Ben,
Attached is a (possible) fix for your previous fix to enable legacy
include paths (which still didn't work for me).
I'm not sure this patch is totally safe because it refers to
$(top_srcdir), i.e. where the SVN checkout of libmesh resides.
Do we have to assume the user can delete their $(to
On Tue, Nov 20, 2012 at 4:23 PM, John Peterson wrote:
> Attached is a (possible) fix for your previous fix to enable legacy
> include paths (which still didn't work for me).
I guess I could elaborate. The problem seems to be that
${INSTALL_DIR}/lib/x86_64-apple-darwin10.8.0_opt/pkgconfig/Make.c
On Nov 20, 2012, at 5:23 PM, John Peterson wrote:
> Ben,
>
> Attached is a (possible) fix for your previous fix to enable legacy
> include paths (which still didn't work for me).
>
> I'm not sure this patch is totally safe because it refers to
> $(top_srcdir), i.e. where the SVN checkout of lib
Buildbot's not finding it, at least.
---
Roy
--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc
"make run_examples" now redirects each example's output to a
test-suite.log file; can we "tee" it there instead, at least when only
one example at a time is being run? It's much easier (even from the
terminal, much less from buildbot's web interface!) to examine example
output when we've got more
Granted, we never had enough unit tests, but it was still better than
our current effective "zero". ;-)
---
Roy
--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight i
14 matches
Mail list logo
