and I *believe* but could be wrong that its better to have it point to /usr/lib/libgcc_s.1.dylib or something?
otoh, the otool -L output of those respective things are VERY different
People will need to have that libgcc_s.1.dylib *by path* installed. Apple's is likely too old to be compatible, so copying it or using install_name_tool to repoint to it will likely lead to a non-working program.
You mentioned at one point that you built using a local gcc install. gcc uses its bundled libgcc_s; so you will have that dependency unless you switch to /usr/bin/clang to build.