Re: [gentoo-embedded] /lib/libgcc_s.so.1 does not belong to any package?

[Joakim Tjernlund]

Mike Frysinger <vapier@g.o> wrote on 2012/03/14 20:30:24:
>
> On Wednesday 14 March 2012 05:32:35 Joakim Tjernlund wrote:
> > Mike Frysinger <vapier@g.o> wrote on 2012/03/13 23:47:27:
> > > On Tuesday 13 March 2012 08:43:16 Joakim Tjernlund wrote:
> > > > Ed W <lists@××××××××××.com> wrote on 2012/03/13 13:07:37:
> > > > > On 10/03/2012 20:58, Mike Frysinger wrote:
> > > > > > On Friday 09 March 2012 10:58:10 Joakim Tjernlund wrote:
> > > > > >> A "qfile /lib/libgcc_s.so.1" does not list any package,
> > > > > >> should it not belong to sys-devel/gcc ?
> > > > > >
> > > > > > gcc-config installs it from /usr/lib/gcc/..... to /lib
> > > > >
> > > > > So perhaps there is a case that gcc-config/eselect/webapp-config/etc
> > > > > should record what they do..?
> > > >
> > > > Would help some, I just noted that gcc-config does not install
> > > > libgcc_s.so.1 for cross gccs, a bug?
> > >
> > > not sure what you mean.  afaik, it works fine.
> >
> > gentoo-qclli gcc # gcc-config powerpc-softfloat_4.5.3-linux-gnu-4.5.3
> >  * Switching cross-compiler to powerpc-softfloat_4.5.3-linux-gnu-4.5.3 ...
> >       [ ok ]
> > gentoo-qclli gcc # find /usr/powerpc-softfloat_4.5.3-linux-gnu/ -name
> >    "libgcc_s.*"
> > gentoo-qclli gcc #
> >
> > Should it not be a libgcc_s under there?
>
> no.  again, context matters.  what you did above was pick a cross-compiler
> (CHOST=x86_64-pc-linux-gnu/whatever CTARGET=powerpc-xxx).  you did not pick a
> native compiler and that is the only time libgcc_s and friends get copied.
>
> had you installed a native compiler into /usr/$CTARGET and then done something
> like `ROOT=/usr/$CTARGET gcc-config $CTARGET-ver`, you'd probably get a
> libgcc_s in /usr/$CTARGET/lib/.
> -mike

Sorry for the late reply, got sidetracked.

What bugs me is that one can generally use /usr/$CTARGET as your root fs on
your favourite embedded target. Doing so will loose libgcc_s.so as there isn't one
installed. Having to install gcc into /usr/$CTARGET just to get libgcc_s is
a bit much.

Also, would it not be better if glibc showed up in
 export ROOT=/usr/${CTARGET} PKGDIR=${PORTDIR}/pkgs/${CTARGET}/pkgs quickpkg `qlist -IC`
instead of
 export ROOT=/ PKGDIR=${PORTDIR}/pkgs/${CTARGET}/cross-tools quickpkg `qlist -IC cross-${CTARGET}`
?

 Jocke