public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant <emailgrant@gmail.com>
To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] What is libgcc_s.so.1?
Date: Wed, 21 Nov 2012 14:09:03 -0800	[thread overview]
Message-ID: <CAN0CFw3D_ySxieW9Mnq-0TLZcQsSi=24_hi6-rH3YtTWxSii8g@mail.gmail.com> (raw)
In-Reply-To: <20121121235737.28061d6b@khamul.example.com>

[-- Attachment #1: Type: text/plain, Size: 2330 bytes --]

> > 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

[-- Attachment #2: Type: text/html, Size: 2894 bytes --]

  reply	other threads:[~2012-11-21 22:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-21 21:25 [gentoo-user] What is libgcc_s.so.1? Grant
2012-11-21 21:56 ` Bruce Hill
2012-11-21 21:57 ` Alan McKinnon
2012-11-21 22:09   ` Grant [this message]
2012-11-21 22:17     ` Michael Mol

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAN0CFw3D_ySxieW9Mnq-0TLZcQsSi=24_hi6-rH3YtTWxSii8g@mail.gmail.com' \
    --to=emailgrant@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox