Trac

trac@lists.einsteintoolkit.org

8708 discussions

#2526: McLachlan has incorrect READ declarations for presync.
by Roland Haas 06 Apr '23

06 Apr '23

#2526: McLachlan has incorrect READ declarations for presync. Reporter: Peter Diener Status: new Milestone: ET_2021_05 Version: development version Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): I believe this Kranc pull request addresses the issue: [https://github.com/ianhinder/Kranc/pull/155](https://github.com/ianhinder/K… -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2526/mclachlan-has-inc…

1 0

#2525: ET website "capabilities" page only lists McLachlan but not lean_public or Baikal
by Roland Haas 06 Apr '23

06 Apr '23

#2525: ET website "capabilities" page only lists McLachlan but not lean_public or Baikal Reporter: Roland Haas Status: new Milestone: Version: development version Type: bug Priority: minor Component: EinsteinToolkit website Comment (by Roland Haas): @{557058:8bc23f2a-45c0-477d-8ac4-a5a16c734278} @{557058:a2800088-fc6e-4fbe-9a1e-663271f736bd} would you like to add descriptions of Baikal and lean\_public as indicated in [https://bitbucket.org/einsteintoolkit/tickets/issues/2525/et-website-capabi… ? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2525/et-website-capabi…

1 0

#2661: failure to regenerate Baikal and BaikalVacuum parfiles from README instruction
by Roland Haas 06 Apr '23

06 Apr '23

#2661: failure to regenerate Baikal and BaikalVacuum parfiles from README instruction Reporter: Status: new Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): @{557058:8bc23f2a-45c0-477d-8ac4-a5a16c734278} Any updates on this? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2661/failure-to-regene…

1 0

#2660: create autoconf test that checks for too old g++ STL in combination with icpc
by Roland Haas 06 Apr '23

06 Apr '23

#2660: create autoconf test that checks for too old g++ STL in combination with icpc Reporter: Roland Haas Status: duplicate Milestone: Version: Type: task Priority: minor Component: Changes (by Roland Haas): status: duplicate (was new) Comment (by Roland Haas): Duplicate of #2663. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2660/create-autoconf-t…

1 0

#2648: Empty ApplyBCs call in LeanBSSNMoL
by Roland Haas 06 Apr '23

06 Apr '23

#2648: Empty ApplyBCs call in LeanBSSNMoL Reporter: Samuel Cupp Status: resolved Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Changes (by Roland Haas): status: resolved (was new) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2648/empty-applybcs-ca…

1 0

#1658: ExternalLibraries/pciutils does not compile on Mac OS
by Roland Haas 06 Apr '23

06 Apr '23

#1658: ExternalLibraries/pciutils does not compile on Mac OS Reporter: Ian Hinder Status: resolved Milestone: Version: development version Type: bug Priority: minor Component: Cactus Changes (by Roland Haas): status: resolved (was open) When I try to compile ExternalLibraries/pciutils on Mac OS, I get lspci.c:919:29: error: expected ')' puts("lspci version " PCIUTILS_VERSION); ^ ./pciutils.h:18:26: note: expanded from macro 'PCIUTILS_VERSION' #define PCIUTILS_VERSION PCILIB_VERSION ^ lspci.c:919:11: note: to match this '(' puts("lspci version " PCIUTILS_VERSION); This is with the osx-mountain-lion-macports-gcc.cfg optionlist, and "gcc-mp-4.6 (MacPorts gcc46 4.6.4_3) 4.6.4". I have to disable this thorn in my thornlist (or machine definition file) to compile the ET. This means that the ET will not compile out of the box on Mac OS. **Keyword:** -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/1658/externallibraries…

1 0

#2705: error: more than one instance of overloaded function "isnan" matches the argument list
by Roland Haas 06 Apr '23

06 Apr '23

#2705: error: more than one instance of overloaded function "isnan" matches the argument list Reporter: Miguel Zilhão Status: new Milestone: Version: Type: bug Priority: major Component: Comment (by Roland Haas): I am proposing an automated test \(and thus better error message\) for this in [#2663](https://bitbucket.org/einsteintoolkit/tickets/issues/2663/add-an-notice-about-minimum-intel-gcc). Feel free to review. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2705/error-more-than-o…

1 0

#2663: add an notice about minimum Intel / GCC version required to configure output
by Roland Haas 06 Apr '23

06 Apr '23

#2663: add an notice about minimum Intel / GCC version required to configure output Reporter: Roland Haas Status: new Milestone: Version: Type: enhancement Priority: major Component: Comment (by Roland Haas): Please review. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2663/add-an-notice-abo…

1 0

#2663: add an notice about minimum Intel / GCC version required to configure output
by Roland Haas 06 Apr '23

06 Apr '23

#2663: add an notice about minimum Intel / GCC version required to configure output Reporter: Roland Haas Status: new Milestone: Version: Type: enhancement Priority: major Component: Comment (by Roland Haas): Pull request to test for C\+\+11 math for isnan is here: [https://bitbucket.org/cactuscode/cactus/pull-requests/152](https://bitbucke… This is probably better than trying to rely on feature test macros since those may not really tell the truth due to bugs in c\+\+ libraries. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2663/add-an-notice-abo…

1 0

#2705: error: more than one instance of overloaded function "isnan" matches the argument list
by Roland Haas 06 Apr '23

06 Apr '23

#2705: error: more than one instance of overloaded function "isnan" matches the argument list Reporter: Miguel Zilhão Status: new Milestone: Version: Type: bug Priority: major Component: Comment (by Roland Haas): uh there may be a way around. Though it would require that we added extra `#ifdef` to the code and the point of this was more or less to not have those around anymore. Nope, no luck. I took a look at the ticket where this was initial discussed: [https://bitbucket.org/einsteintoolkit/tickets/issues/2407/cactus-math-work-… and keeping workarounds was considered optional and since we never ran into issues on “supported” clusters they were not implemented. I think you may stand a good chance asking the admins to install a newer gcc for you since gcc 4.X is really very old. In particular if you can point them to the Intel docs stating that g\+\+'s STL is needed for icpc \(see eg [https://www.intel.com/content/www/us/en/developer/articles/release-notes/c-… for intel 2019 and its requirements\). If all else fails, you can also compile your own g\+\+ and use that. Usually following the instructions at [https://gcc.gnu.org/install/download.html](https://gcc.gnu.org/install/down… , [https://gcc.gnu.org/install/configure.html](https://gcc.gnu.org/install/con… , and [https://gcc.gnu.org/install/build.html](https://gcc.gnu.org/install/build.h… \(very carefully! note the `build` directory and the `contrib/download_prerequisites` script\) works \(it will take a while though\) and afterwards you can pass the `-gxx-name <path-to-g++>` option to `icpc` to make it use the new stdc\+\+ library. You can also experiment with using `spack` to install `gcc` \(which is easier, but just as slow\). [https://spack-tutorial.readthedocs.io/en/latest/tutorial\_basics.html](http… ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2705/error-more-than-o…

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac