Trac January 2023

trac@lists.einsteintoolkit.org

1 participants
91 discussions

#2679: How to link an externally compiled library during ET compilation
by Roland Haas 09 Jan '23

09 Jan '23

#2679: How to link an externally compiled library during ET compilation Reporter: Maria Mutz Status: open Milestone: Version: Type: bug Priority: minor Component: Changes (by Roland Haas): status: open (was new) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2679/how-to-link-an-ex…

1 0

#2679: How to link an externally compiled library during ET compilation
by Roland Haas 09 Jan '23

09 Jan '23

#2679: How to link an externally compiled library during ET compilation Reporter: Maria Mutz Status: new Milestone: Version: Type: bug Priority: minor Component: Comment (by Roland Haas): This is rather strange. The optioin list looks ok to me to be honest. Adding `-lcocalmrns` to `LDFLAGS` is ok. The error message about missing `main` is strange since `main` is provided by the Cactus flesh. Is it possible that the COCAL library defines its own `main` and that that one interferes? It would be good to see all the error messages and not just the last couple. Would you mind taking a look at [http://einsteintoolkit.org/support.html#general-guidelines-for-questions](h… and provide the files described in there, please? Since COCAL is not part of the Einstein Toolkit \(and, at least until the recent past, had an unusual build system\), have you contacted the COCAL author \(Antonios Toskaros\), who may be able to provide advise as well? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2679/how-to-link-an-ex…

1 0

#2679: How to link an externally compiled library during ET compilation
by Roland Haas 09 Jan '23

09 Jan '23

#2679: How to link an externally compiled library during ET compilation Reporter: Maria Mutz Status: new Milestone: Version: Type: bug Priority: minor Component: Changes (by Roland Haas): responsible: [] (was ) component: (was EinsteinToolkit thorn) priority: minor (was major) assignee: Roland Haas (was ) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2679/how-to-link-an-ex…

1 0

#2679: How to link an externally compiled library during ET compilation
by Maria Mutz 07 Jan '23

07 Jan '23

#2679: How to link an externally compiled library during ET compilation Reporter: Maria Mutz Status: new Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn I have compiled the COCAL code separately from the ET, generating a library for which I have the .a file. I’m trying to link to that library when compiling the ET on Expanse. When I try to link it without copying all the source files in the thorn that uses it into the src directory I get “undefined reference to” errors for anything in a subdirectory. I tried moving all the files in subdirectories into the src directory as a work-around, but then I started getting errors that look like this: ‌ ‌ \`\`\` ‌ /lib/../lib64/crt1.o: In function \`\_start': \(.text\+0x24\): undefined reference to \`main' collect2: error: ld returned 1 exit status make\[3\]: \*\*\* \[<builtin>: include\_modulefiles\_MRNS.f90\] Error 1 make\[2\]: \*\*\* \[/home/mmutz/Cactus/lib/make/make.thornlib:113: make.checked\] Error 2 make\[1\]: \*\*\* \[/home/mmutz/Cactus/lib/make/make.configuration:179: /home/mmutz/Cactus/configs/sim17/lib/libthorn\_Cocalthorn.a\] Error 2 \`\`\` ‌ What is the proper way to link the library during compilation? I’ve attached a copy of my config file. ‌ attachment: OptionList.pdf (https://api.bitbucket.org/2.0/repositories/einsteintoolkit/tickets/issues/2…) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2679/how-to-link-an-ex…

1 0

#2678: clean up GRHydro schedule file
by Roland Haas 05 Jan '23

05 Jan '23

#2678: clean up GRHydro schedule file Reporter: Roland Haas Status: new Milestone: Version: Type: enhancement Priority: trivial Component: Comment (by Roland Haas): Please review -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2678/clean-up-grhydro-…

1 0

#2678: clean up GRHydro schedule file
by Roland Haas 05 Jan '23

05 Jan '23

#2678: clean up GRHydro schedule file Reporter: Roland Haas Status: new Milestone: Version: Type: enhancement Priority: trivial Component: Changes (by Roland Haas): responsible: [] (was ) assignee: Roland Haas (was ) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2678/clean-up-grhydro-…

1 0

#2678: clean up GRHydro schedule file
by Roland Haas 05 Jan '23

05 Jan '23

#2678: clean up GRHydro schedule file Reporter: Roland Haas Status: new Milestone: Version: Type: enhancement Priority: trivial Component: GRHydro currently: * schedules storage for `conformal_state` which it no longer uses \(since git hash [8a91441](https://bitbucket.org/einsteintoolkit/einsteinevolve/commits/8a914… "GRHydro: \* remove dependence on StaticConformal \* change calculation of the determinant of the 3-metric from a subroutine call to a macro." of [einsteinevolve](https://bitbucket.org/einsteintoolkit/einsteinevolve)\) * tries to register its banner in WRAGH which is too late, it must be done in STARTUP \([http://einsteintoolkit.org/referencemanual/ReferenceManual.html#x1-174000A2](http://einsteintoolkit.org/referencemanual/ReferenceManual.html#x1-174000A2)\) Pull request [https://bitbucket.org/einsteintoolkit/einsteinevolve/pull-requests/20](http… fixes these. ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2678/clean-up-grhydro-…

1 0

#1713: Avoid build-time warning
by Roland Haas 05 Jan '23

05 Jan '23

#1713: Avoid build-time warning Reporter: Erik Schnetter Status: open Milestone: Version: development version Type: bug Priority: minor Component: EinsteinToolkit thorn Comment (by Roland Haas): Please review -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/1713/avoid-build-time-…

1 0

#1713: Avoid build-time warning
by Roland Haas 05 Jan '23

05 Jan '23

#1713: Avoid build-time warning Reporter: Erik Schnetter Status: open Milestone: Version: development version Type: bug Priority: minor Component: EinsteinToolkit thorn Comment (by Roland Haas): Pull request is here: [https://bitbucket.org/einsteintoolkit/einsteinevolve/pull-requests/19](http… -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/1713/avoid-build-time-…

1 0

#2672: obtain DNS enty to point https://tests.einsteintoolkit.org to https://einsteintoolkit.github.io/tests
by Roland Haas 05 Jan '23

05 Jan '23

#2672: obtain DNS enty to point https://tests.einsteintoolkit.org to https://einsteintoolkit.github.io/tests Reporter: Roland Haas Status: new Milestone: Version: Type: enhancement Priority: minor Component: EinsteinToolkit website Comment (by Roland Haas): @{557058:1671c5c3-29cc-4e83-9850-a152d33a6235} do you think this something that could be done? Needs a DNS entry set by LSU \(I recall a statement somehwere that LSU policy prohibits pointing a DNS entry to a server not controlled by LSU but then it seemed to have been fine for cactuscode.org\). -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2672/obtain-dns-enty-t…

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac January 2023