> > I'm building a minimal Gentoo system but I always get the following > > error when I try to chroot into the final system: > > > > /bin/bash: error while loading shared libraries: libgcc_s.so.1: > > cannot open shared object file: No such file or directory > > > > I ran 'equery > > b /usr/lib64/gcc/x86_64-pc-linux-gnu/4.5.4/libgcc_s.so.1' on one of > > my conventionally-built Gentoo systems and the file isn't determined > > to belong to any package. > > > > Where does this file come from and how can I add it to my > > manually-built Gentoo system? > > > > I'm following these instructions to build the minimal Gentoo system: > > > > http://judepereira.com/blog/going-embedded-with-mgentoo/ > > > > ROOT=/mounted/ emerge -auvND baselayout uclibc bash dropbear pam udev > > iptables coreutils nano util-linux shadow kbd net-tools grep procps > > gzip sed findutils mawk htop > > > > - Grant > > 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. Does this basically mean I must install gcc in order to have a working system? Jude doesn't install gcc but he doesn't know why I'm getting that error. I thought gcc was only necessary for compiling. - Grant