#2773: make CarpetX-ThornDoc is confused in InterLatex.pl
Reporter: Roland Haas
Status: open
Milestone:
Version:
Type: bug
Priority: minor
Component: Cactus
Changes (by Roland Haas):
responsible: [] (was )
assignee: Steven R. Brandt (was )
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2773/make-carpetx-thor…
#2773: make CarpetX-ThornDoc is confused in InterLatex.pl
Reporter: Roland Haas
Status: new
Milestone:
Version:
Type: bug
Priority: minor
Component: Cactus
Running `make CarpetX-ThornDoc` I find warnings \(among others…\) in `LOG_INTERLATEX_MSGS`:
```
ekohaes8: .../cactus/CarpetXCPU$ less doc/ThornDoc/CarpetX/CarpetX/LOG_INTERLATEX_MSGS
CarpetX
Parsing interface for CarpetX
Initialized thorn structure for CarpetX
Implements: CarpetX
Inherits: IO
2 Public, 0 Protected, 0 Private variable groups
Walking ancestors for CarpetX
--> Confused: [global_type] = [HASH(0x560e5bfd79e8)]
Finished.
```
which is due to a hash membmer `global_type` \(a bareword\) in the `interface_db`.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2773/make-carpetx-thor…
#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 Steven R. Brandt):
I’ve had trouble controlling the linking process on multiple occasions. It would be nice to have more control over it.
--
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
Comment (by Roland Haas):
Is dislike both :-\) But, as @{557058:1671c5c3-29cc-4e83-9850-a152d33a6235} , will be happy to confirm, that is my default answer and may well change.
Let me think about this a bit. I would have hoped using `LDFLAGS` would have worked, but this does not seem to be the case for you.
--
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
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…