I am new to MacPorts, so please excuse if this is dumb question. 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$ If I run /opt/local/bin/bash another level deeper, then that instance of bash works as expected without crashing… So what do I need to do in order to use /opt/local/bin/bash as my primary login shell under Terminal.app? My suspicion is that when it’s first launched, it does not have /opt/local in the path yet until .bashrc is loaded later. And so I’m theorizing that it’s linking up the wrong libraries or something from my MacOS Sequoia system. On the other hand once I’m in the broken shell, how the path is set from .bashrc, so running bash again, then links up the second bash instance with the right underlying libs. Just guessing out loud… But anyone know what we need to do in order to use /opt/local/bin/bash as primary shell from Terminal.app?
