On Nov 28, 2024, at 20:48, Steve Schow wrote: > I am new to MacPorts, so please excuse if this is dumb question.
Welcome! Not a dumb question at all, just a bug. > I installed macports bash with the intention to use it as my primary shell > with Terminal.app. But when I configured Terminal to use /opt/local/bin/bash > as the shell, then I get crashing behavior. Specifically I can launch the > terminal new window, it will open up the terminal window with bash running. > However if I type in an unknown command, it crashes with the following: > > Steves-MacBook-Air:~ sjs$ lasdfasdf > objc[61030]: +[Swift.__SharedStringStorage initialize] may have been in > progress in another thread when fork() was called. > objc[61030]: +[Swift.__SharedStringStorage initialize] may have been in > progress in another thread when fork() was called. We cannot safely call it > or ignore it in the fork() child process. Crashing instead. Set a breakpoint > on objc_initializeAfterForkError to debug. > Abort trap: 6 > Steves-MacBook-Air:~ sjs$ This is https://trac.macports.org/ticket/68638 > I’m theorizing that it’s linking up the wrong libraries or something from my > MacOS Sequoia system. That's not possible; that's not how dynamic libraries work on macOS. They're always referenced by absolute path, as you can see with the "otool -L" output shown in the previous reply. Your PATH has no influence over library loading, only over the finding of binaries and man pages.
