Trac March 2014

trac@lists.einsteintoolkit.org

1 participants
137 discussions

[Einstein Toolkit] #1559: Replace deprecated use of finite() in AEILocalInterp
by Einstein Toolkit 15 Mar '14

15 Mar '14

#1559: Replace deprecated use of finite() in AEILocalInterp -----------------------------------+---------------------------------------- Reporter: barry.wardell | Owner: Type: defect | Status: new Priority: major | Milestone: Component: EinsteinToolkit thorn | Version: development version Keywords: | -----------------------------------+---------------------------------------- My compiler (gcc 4.8) warns when compiling AEILocalInterp that it is using a deprecated function finite(). Apparently this is not part of any C standard and should be replaced by the C99 isfinite() function. The attached patch replaces the usage of finite() with isfinite() in AEILocalInterp. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1559> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #882: Create ThornGuideHTML target
by Einstein Toolkit 14 Mar '14

14 Mar '14

#882: Create ThornGuideHTML target ----------------------+----------------------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: Cactus | Version: Keywords: | ----------------------+----------------------------------------------------- Barry Wardell suggests: The only issue is that there doesn't seem to be a HTML version of the configuration specific ThornGuide make target, so we should add this as a target at the same time as removing the patch. I'd imagine this would just be a matter of copy-and-paste from the existing ThornGuideHTML target. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/882> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #1489: EinsteinExact (the arrangement) fails to build ThornGuideHTML
by Einstein Toolkit 14 Mar '14

14 Mar '14

#1489: EinsteinExact (the arrangement) fails to build ThornGuideHTML -----------------------------------+---------------------------------------- Reporter: knarf | Owner: Type: defect | Status: new Priority: major | Milestone: ET_2014_05 Component: EinsteinToolkit thorn | Version: development version Keywords: | -----------------------------------+---------------------------------------- EinsteinExact (the arrangement) fails to build ThornGuideHTML. The problem is the file spacetimes.tex which is included, but ThornGuideHTML is built outside of the doc directory, and cannot find it. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1489> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 6

[Einstein Toolkit] #1511: links in web-thornguide lead to incorrect thornguide
by Einstein Toolkit 14 Mar '14

14 Mar '14

#1511: links in web-thornguide lead to incorrect thornguide -------------------------------------+-------------------------------------- Reporter: rhaas | Owner: Type: defect | Status: new Priority: major | Milestone: Component: EinsteinToolkit website | Version: development version Keywords: thornguide | -------------------------------------+-------------------------------------- the online version of the thornguide seems to contain a correct table of content. Clicking eg on the CoreDoc link in http://einsteintoolkit.org/documentation/ThornGuide/ThornGuide.html brings me to http://einsteintoolkit.org/documentation/ThornGuide/ThornGuidech20.html#x26… which seems to be the documentation for EllSOR. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1511> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #1556: Online Thorn Guide broken
by Einstein Toolkit 14 Mar '14

14 Mar '14

#1556: Online Thorn Guide broken ----------------------------------------+----------------------------------- Reporter: joachim.frieben@… | Owner: Type: defect | Status: new Priority: major | Milestone: Component: EinsteinToolkit website | Version: Keywords: broken index | ----------------------------------------+----------------------------------- Browsing the online documentation for the various thorns it turns out that the index at http://einsteintoolkit.org/documentation/ThornGuide/ThornGuide.html is broken for "Part F CactusElliptic" which points instead to "Part F CactusIO" and similarly for everything that follows. This makes the web page pretty much unusable .. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1556> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 30

[Einstein Toolkit] #1522: Improve determining make dependencies
by Einstein Toolkit 13 Mar '14

13 Mar '14

#1522: Improve determining make dependencies -------------------------+-------------------------------------------------- Reporter: eschnett | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: Cactus | Version: development version Keywords: | -------------------------+-------------------------------------------------- Cactus automatically determines the dependencies between source files and their include files. This mechanism doesn't quite work in all cases; e.g. when a source file (or header file?) is removed, the build aborts, and the auto-generated dependencies have to be deleted automatically. I have recently come across a mechanism that works reliably. Here is the relevant Makefile fragment, applied to building C++ files: {{{ # Taken from <http://mad-scientist.net/make/autodep.html> as written # by Paul D. Smith <psmith(a)gnu.org>, originally developed by Tom # Tromey <tromey(a)cygnus.com> PROCESS_DEPENDENCIES = \ sed -e 's/$@.tmp/$@/g' < $*.o.d > $*.d && \ sed -e 's/\#.*//' \ -e 's/^[^:]*: *//' \ -e 's/ *\\$$//' \ -e '/^$$/ d' \ -e 's/$$/ :/' < $*.o.d >> $*.d && \ rm -f $*.o.d %.o: %.cc ${CXX} -MD ${CPPFLAGS} ${CXXFLAGS} -o $@.tmp -c $*.cc @${PROCESS_DEPENDENCIES} @mv $@.tmp $@ -include ${DEPS} }}} -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1522> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 16

[Einstein Toolkit] #1553: Prevent the user defining non-static functions in more than one object file
by Einstein Toolkit 11 Mar '14

11 Mar '14

#1553: Prevent the user defining non-static functions in more than one object file -------------------------+-------------------------------------------------- Reporter: hinder | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Cactus | Version: development version Keywords: | -------------------------+-------------------------------------------------- If a non-static function is defined in more than one object file, the results at run-time are unexpected or unpredictable. I was under the impression that there were compiler options to prevent this. At least on Mac OS, these must not be used, as I just ran into this problem. So, either we find out which options are needed and add them, or we could provide some additional checks in the build system to help catch this error. For example, Cactus scheduled functions defined with the same name should be easy to catch. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1553> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac March 2014