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: Douglas Campos <qmx2352@...>
Subject: Re: crossdev fails on gcc-stage1
Date: Wed, 25 Jan 2006 08:45:51 -0200
<div>I've heard that crossdev was deprecated</div>
<div>Anyone has more info?<br><br>&nbsp;</div>
<div><span class="gmail_quote">On 1/24/06, <b class="gmail_sendername"><a href="mailto:sraczynski@...">sraczynski@...</a></b> &lt;<a href="mailto:sraczynski@...">sraczynski@...</a>&gt; wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Recently I ran onto a really depressing problem with crossdev. It fails to emerge stage1 of gcc, no matter what version of gcc I tell it to compile (
2.95, 3.2.x, 3.4.x, 4.0.0, you name it). I have this problem on every three computers I've tried (x86 and two amd64s). It usually ends in the middle of emerging with a &quot;configure: error: unknown endianess - sorry&quot;. What I run is:
<br><br>crossdev -t arm-unknown-linux-uclibc<br><br>I'm out of ideas. Please help.<br><br>Best wishes,<br>Stanislaw Raczynski<br>--<br><a href="mailto:gentoo-embedded@g.o">gentoo-embedded@g.o</a> mailing list
<br><br></blockquote></div><br>
Replies:
Re: crossdev fails on gcc-stage1
-- Mike Frysinger
References:
crossdev fails on gcc-stage1
-- sraczynski
Navigation:
Lists: gentoo-embedded: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
crossdev fails on gcc-stage1
Next by thread:
Re: crossdev fails on gcc-stage1
Previous by date:
Re: moving uClibc 0.9.28 to stable
Next by date:
Re: crossdev fails on gcc-stage1


Updated Jun 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.