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: gentoo-embedded@g.o
From: Mike Frysinger <vapier@g.o>
Subject: Re: crossdev messes up system headers, etc
Date: Thu, 19 Oct 2006 18:23:34 -0400
On Thursday 19 October 2006 14:35, Christopher Friedt wrote:
> after that, i attempted to emerge another package. After a couple of
> tries, i noticed the same errors.
>
> It turns out that crossdev had done something unexpected, and removed
> several system headers, and left my machine in a pretty useless state
> for development. I can no longer compile anything, not even a kernel.

if you read the code, it only deletes files with CTARGET in them and any 
recursive operations are done with `rm -i`

you'd have to give more info than "it deleted things"

> So obviously, I'd like to ask anyone for some sort of suggestion to get
> my native development chain back.

you can just grab a stage3, create bin pkgs, and then use them

> Why is crossdev in production if it does these sort of things?

no point in responding to such a lame question
-mike
Attachment:
pgpSA0Oc9hQns.pgp (PGP signature)
References:
RE: C++ Exceptions Call Abort With Toolchain generated by crossdev
-- Ryan Baldwin
crossdev messes up system headers, etc
-- Christopher Friedt
Navigation:
Lists: gentoo-embedded: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
crossdev messes up system headers, etc
Next by thread:
Emerge Bash has Problems linking libgcc.a
Previous by date:
crossdev messes up system headers, etc
Next by date:
[x86-uclibc-2006.1] GCC-4.1.x + uClibc-0.9.28 + procps-3.2.x = Segmentation Fault ?


Updated Sep 17, 2009

Summary: Archive of the gentoo-embedded mailing list.

Donate to support our development efforts.

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