It comes from gcc. The ebuild install to /usr/lib, not /usr/lib64 like
you searched for (one dir is a symlink to the other to make stuff work.)
The only reference to libgcc_s in the ebuild comes from the toolchain
eclass:
# libgcc_s and, with gcc>=4.0, other libs get installed in multilib specific locations by gcc
# we pull everything together to simplify working environment
if has_multilib_profile ; then
case $(tc-arch) in
amd64)
mv "${D}${LIBPATH}"/../$(get_abi_LIBDIR amd64)/* "${D}${LIBPATH}"
mv "${D}${LIBPATH}"/../$(get_abi_LIBDIR x86)/* "${D}${LIBPATH}"/32
;;
ppc64)
# not supported yet, will have to be adjusted when we
# actually build gnat for that arch
;;
esac
fi
And that looks like it needs a multilib profile.
Dunno how much if any that will help you.
--
Alan McKinnon
alan.m...@gmail.com