Trac

trac@lists.einsteintoolkit.org

8708 discussions

#2837: Building the Einstein Toolkit
by Suo-Ning Wang 19 Dec '24

19 Dec '24

#2837: Building the Einstein Toolkit Reporter: Suo-Ning Wang Status: open Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit website Comment (by Suo-Ning Wang): Hello Roland Haas, I have solved the libsz. But I build the toolkit on Ubuntu and Opensuse, but both of them have other problems. I have uploaded two different make.log to the attachment. Due to the time difference between us, I apologize for not being able to communicate with you in a timely manner as I replied to your message before I went to bed. Thank you again. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2837/building-the-eins…

1 0

#2835: add backtrace functionality from CarpetLib
by Roland Haas 18 Dec '24

18 Dec '24

#2835: add backtrace functionality from CarpetLib Reporter: Roland Haas Status: open Milestone: Version: development version Type: enhancement Priority: major Component: EinsteinToolkit thorn Changes (by Roland Haas): status: open (was new) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2835/add-backtrace-fun…

1 0

#2835: add backtrace functionality from CarpetLib
by Roland Haas 18 Dec '24

18 Dec '24

#2835: add backtrace functionality from CarpetLib Reporter: Roland Haas Status: new Milestone: Version: development version Type: enhancement Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): Please review. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2835/add-backtrace-fun…

1 0

#2835: add backtrace functionality from CarpetLib
by Roland Haas 18 Dec '24

18 Dec '24

#2835: add backtrace functionality from CarpetLib Reporter: Roland Haas Status: new Milestone: Version: development version Type: enhancement Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): @{557058:56049c54-f8c2-4b6c-9b88-ab697c967495} suggested a separate thorn. Here’s one: [https://bitbucket.org/cactuscode/cactusutils/pull-requests/44](https://bitb… -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2835/add-backtrace-fun…

1 0

#2837: Building the Einstein Toolkit
by Roland Haas 18 Dec '24

18 Dec '24

#2837: Building the Einstein Toolkit Reporter: Suo-Ning Wang Status: open Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit website Comment (by Roland Haas): Ok, this seems to not find libsz: ``` libtool: link: g++ -g -std=c++17 -D_GNU_SOURCE -O2 -fopenmp -Wall -rdynamic -Wl,-rpath -Wl,/usr/lib64/gcc/x86_64-suse-linux/14 -o silock silock.o -L/usr/lib64/gcc/x86_64-suse-linux/14 -L/usr/gapps/silo/szip/2.1/i386-pc-linux-gcc-3.2.3/lib ../../src/.libs/libsilo.a -lhdf5hl_fortran -lhdf5_fortran -lhdf5_hl -lhdf5 -lz -lcrypt -lgfortran -lm -lsz -fopenmp /usr/lib64/gcc/x86_64-suse-linux/14/../../../../x86_64-suse-linux/bin/ld: cannot find -lsz: No such file or directory ``` which I have seen on some systems where `libsz` in located in the “usual” locations or not the ones reported by pkg-config. This path looks suspicious: `/usr/gapps/silo/szip/2.1/i386-pc-linux-gcc-3.2.3/lib` since your system should be am64 or x86\_64 and not i386 \(32bit\). I have no idea where it got that one from though \(the log file says it is a default path provided, but I don’t know who or what may have provided it\). One way to work around this may be to find out where the file `libsz.a` is located and at the _directory_ it is in to \(or add an entry with if not yet there\) to the `LIBDIRS` variable in generic.cfg \(and compile from scratch\). So ``` LIBDIRS=<path-to-directory-with-libsz.a> ``` may work for you. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2837/building-the-eins…

1 0

#2837: Building the Einstein Toolkit
by Suo-Ning Wang 18 Dec '24

18 Dec '24

1 0

#2837: Building the Einstein Toolkit
by Suo-Ning Wang 18 Dec '24

18 Dec '24

#2837: Building the Einstein Toolkit Reporter: Suo-Ning Wang Status: open Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit website Comment (by Suo-Ning Wang): <div class="preview-container wiki-content"></div> <div class="mask"></div> </div> </div> </form> -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2837/building-the-eins…

1 0

#2837: Building the Einstein Toolkit
by Suo-Ning Wang 18 Dec '24

18 Dec '24

#2837: Building the Einstein Toolkit Reporter: Suo-Ning Wang Status: open Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit website Comment (by Suo-Ning Wang): Hello Roland Haas, I'm sorry to bother you again. I have download the cmake and my system is based on Opensuse not Ubuntu. Then I build the toolkit and also made some mistake. I attached the make.log on the website and hope you help me. Thank you again. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2837/building-the-eins…

1 0

#2837: Building the Einstein Toolkit
by Roland Haas 17 Dec '24

17 Dec '24

#2837: Building the Einstein Toolkit Reporter: Suo-Ning Wang Status: open Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit website Comment (by Roland Haas): Hello Suo-Ning Wang, hmm, actually looking at the paths in your error message, this is not a personal Ubuntu based laptop, is it? Instead this looks like some share university system where you yourself cannot install cmake. If the system offers “environment modules” \(`module list` / `module load`\) then you can try and see if there is a `cmake` module available \(or, if the system is small enough, the sysadmin may be willing to install a copy of cmake\). If that is not possible then you have to compile your own `cmake`. The easiest way is actually using the EinsteinToolkit where there is a “branch” that provides cmake. To do so please run \(in the same directory where you first ran \`GetComponents\`\): ``` ./GetComponents --no-update https://bitbucket.org/einsteintoolkit/manifest/raw/a3d645186fc84f605ede2103… ``` and after that remove your partially compiled code ``` rm -rf Cactus/configs/sim ``` then compile again using `sim build` as shown in the tutorial. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2837/building-the-eins…

1 0

#2837: Building the Einstein Toolkit
by Roland Haas 17 Dec '24

17 Dec '24

#2837: Building the Einstein Toolkit Reporter: Suo-Ning Wang Status: open Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit website Changes (by Roland Haas): responsible: [] (was ) component: EinsteinToolkit website (was ) version: development version (was ) assignee: Roland Haas (was ) When I am building the Einstein Toolkit, I find some bug which I cannot solve. `./simfactory/bin/sim build -j2 --thornlist thornlists/einsteintoolkit.th` I want to know what went wrong. ![](https://bitbucket.org/repo/8zBLME5/images/709390997-c10063cf-bf10-4b91-beae-14602e5f2850.png) ‌ ![](https://bitbucket.org/repo/8zBLME5/images/3831281540-21b902a3-abf7-44a8-9249-52618111b4d1.png) ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2837/building-the-eins…

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac