Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-embedded
Navigation:
Lists: gentoo-embedded: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: Mike Frysinger <vapier@g.o>
From: Joakim Tjernlund <joakim.tjernlund@...>
Subject: Re: /lib/libgcc_s.so.1 does not belong to any package?
Date: Mon, 19 Mar 2012 19:09:00 +0100
Mike Frysinger <vapier@g.o> wrote on 2012/03/19 01:51:53:
>
> On Sunday 18 March 2012 14:53:44 Joakim Tjernlund wrote:
> > 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.
>
> why does this actually matter ?  as noted, this hack is merely there to
> support a split /usr setup.  if you're using /usr/$CTARGET as your rootfs,
> then you aren't going to have a split /usr, and thus the lib copy is
> unnecessary.

I don't quite understand. If I copy /usr/$CTARGET to my target board
as rootfs there will be no libgcc on my target and NPTL needs it.

>
> > 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}` ?
>
> no.  cross-${CTARGET}/glibc is a cross-compiler glibc, not a native one.  yes,
> you can run it through a script to move things around so that it'd basically
> have the same install as a native glibc, but the existing one is not.
>
> it might be useful to have crossdev automatically inject glibc into
> package.provided for /usr/$CTARGET since attempting to install a native one in
> there will hit conflicts.

hmm, I always viewed glibc under /usr/$CTARGET as a native target glibc which
could be copied to the target directly, but now you say it is not?

So I should continue building glibc under my own tree (that is what I have been doing
but I figured I could optimize away that step)?

 Jocke



Replies:
Re: /lib/libgcc_s.so.1 does not belong to any package?
-- Mike Frysinger
References:
/lib/libgcc_s.so.1 does not belong to any package?
-- Joakim Tjernlund
Re: /lib/libgcc_s.so.1 does not belong to any package?
-- Mike Frysinger
Re: /lib/libgcc_s.so.1 does not belong to any package?
-- Joakim Tjernlund
Re: /lib/libgcc_s.so.1 does not belong to any package?
-- Mike Frysinger
Navigation:
Lists: gentoo-embedded: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: /lib/libgcc_s.so.1 does not belong to any package?
Next by thread:
Re: /lib/libgcc_s.so.1 does not belong to any package?
Previous by date:
Re: /lib/libgcc_s.so.1 does not belong to any package?
Next by date:
Re: /lib/libgcc_s.so.1 does not belong to any package?


Updated Jun 25, 2012

Summary: Archive of the gentoo-embedded mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.