Hi Jean-Paul, thank you, thank you, thank you! I finally got it working! You're script worked with a few adaptions because I'm not using spack views. So I had to copy and paste quite many libraries, set the paths correctly, and then run it in several library directories of different packages where the links were not correct.
Side note: To get the script running I had to change the file format to UNIX. Therefore, open the script with vi and enter :set fileformat=unix in the vi command mode. Then save it :wq! Again, thank you all a lot for your patience and helpfulness! I appreciate it! Alex Jean-Paul Pelteret schrieb am Donnerstag, 1. Oktober 2020 um 22:13:04 UTC+2: > Hi Alexander, > > I am, unfortunately, marginally acquainted with the problem that you’re > facing. I’m not 100% sure, but I believe that this is an upstream problem > that has to do with how these packages are configured for Apple systems. I > too noticed that within a couple of update cycles SuiteSparse, for example, > went from linking fine, to not specifying any path (only a library name) > when linked, to linking with an @rpath placeholder. Here is a silent update > that offered some mitigation for the problem with SuiteSparse, which > probably (?) was released after the Mac package was built: > > https://github.com/DrTimothyAldenDavis/SuiteSparse/commit/f900df09d2ee3f7ecfd9243b69e181d80f720790#diff-d1c5d2f7b51daaca451f6322f8cd89adR59 > > This is a super annoying problem. So what can you do about it? Well, > possibly the quickest solution to your problem lies with a tool called > “install_name_tool”, which allows you to modify the paths of the libraries > that an executable is linked against. I’ve attached a script that I wrote > for myself a while ago because, well, I faced the same issue. If you modify > it appropriately, you can at least use it to build your executable and > modify the locations of the linked libraries before you get to run the > program. It’s not a great solution, and you definitely shouldn’t have to go > this route, but maybe it would at least help you get going while we (or the > dependency maintainers) get to fixing the core issue. > > Jean-Paul > > -- The deal.II project is located at http://www.dealii.org/ For mailing list/forum options, see https://groups.google.com/d/forum/dealii?hl=en --- You received this message because you are subscribed to the Google Groups "deal.II User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to dealii+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dealii/028c4f63-758c-4f36-8937-0e79b08b38d0n%40googlegroups.com.
