#2772: Issues link against Kadath thorns and Intel MKL due to link ordering
Reporter: tootle
Status: new
Milestone:
Version:
Type: bug
Priority: major
Component: EinsteinToolkit thorn
Comment (by tootle):
@{557058:56049c54-f8c2-4b6c-9b88-ab697c967495} @{557058:59e031ba-9bb5-4298-a472-7b99d0ae6f22} Do you have ideas for either solution?
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2772/issues-link-again…
#2772: Issues link against Kadath thorns and Intel MKL due to link ordering
Reporter: tootle
Status: new
Milestone:
Version:
Type: bug
Priority: major
Component: EinsteinToolkit thorn
A recurring issue that keeps coming up with the KadathThorn/Importer is centered around linking when using intel MKL. It is worth noting that this is not restricted to the ETK, but I had not been able to reproduce the error myself until now.
The problem is resolved if I specify all of the dependencies of Kadath in a specific order in the final build command that outputs the cactus executable. e.g, adding the following directly after -lkadath:
```
-lgsl -lgslcblas -lfftw3 -L${MKLROOT}/lib/ -Wl,--start-group -lmkl_intel_lp64 -lmkl_sequential -lmkl_core -lmkl_blacs_intelmpi_lp64 -Wl,--end-group -lgomp -lpthread -lmkl_scalapack_lp64 -lm -ldl
```
results in a working executable on the local HPC in Idaho. Excluding this link order or adding it somewhere else in the command other than directly after -lkadath will result in an executable that yields undefined behavior. Note: the undefined behavior leads to a crash during ID import from all known cases \(in and out of the ETK\) where this problem has come up.
Solution:
1. Ability to specify a controlled link order in the options.cfg file \(LDFLAGS does not work\)
2. Ability to specify a controlled link order during the build script of KadathThorn
‌
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2772/issues-link-again…
#2172: Test "Binary black hole GW150914" example
Reporter: Roland Haas
Status: resolved
Milestone: ET_2023_11
Version: development version
Type: task
Priority: major
Component: EinsteinToolkit website
Comment (by Roland Haas):
Merged. I think you even told me about the pull request. Sorry about that .
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2172/test-binary-black…
#2172: Test "Binary black hole GW150914" example
Reporter: Roland Haas
Status: resolved
Milestone: ET_2023_11
Version: development version
Type: task
Priority: major
Component: EinsteinToolkit website
Comment (by Deborah Ferguson):
Oh sorry, I submitted a pull request but I don’t know if it’s been merged in
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2172/test-binary-black…
#2520: update gauge settings in TOV example to be more typical
Reporter: Roland Haas
Status: new
Milestone: ET_2023_11
Version: development version
Type: enhancement
Priority: major
Component:
Comment (by Samuel Cupp):
@{557058:59e031ba-9bb5-4298-a472-7b99d0ae6f22} I was going through milestone tickets and saw this one. Is this resolved?
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2520/update-gauge-sett…
#2748: Inclusion of SpaceTimeX in Einstein Toolkit
Reporter: Samuel Cupp
Status: new
Milestone:
Version:
Type: enhancement
Priority: major
Component: EinsteinToolkit thorn
Changes (by Samuel Cupp):
milestone: (was ET_2023_11)
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2748/inclusion-of-spac…