From: "Stanisław Raczyński" <sraczynski@op.pl>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] crossdev fails on gcc-stage1
Date: Thu, 26 Jan 2006 20:53:22 +0100 [thread overview]
Message-ID: <43D928B2.80305@op.pl> (raw)
In-Reply-To: <20060126113940Z4002012-31334+307@kps3.test.onet.pl>
OK, everything works fine after upgrading crossdev from 0.9.12 to 0.9.12-r1.
sraczynski@op.pl wrote:
>I've tried arm-unknown-linux-uclibc, armeb-unknown-linux-uclibc, armeb-softfloat-linux-uclibc, with the same result:
>
>...
>checking whether byte ordering is bigendian... cross-compiling...
>unknown
>checking to probe for byte ordering... /usr/armeb-softfloat-linux-uclibc/bin/ld: crt1.o: No such file or directory
>collect2: ld returned 1 exit status
>unknown
>configure: error: unknown endianess - sorry
>...
>
--
gentoo-embedded@gentoo.org mailing list
prev parent reply other threads:[~2006-01-26 19:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 14:29 [gentoo-embedded] crossdev fails on gcc-stage1 sraczynski
2006-01-25 10:45 ` Douglas Campos
2006-01-25 19:45 ` Mike Frysinger
2006-01-25 23:50 ` Daniel Goller
2006-01-26 11:39 ` sraczynski
2006-01-26 19:53 ` Stanisław Raczyński [this message]
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=43D928B2.80305@op.pl \
--to=sraczynski@op.pl \
--cc=gentoo-embedded@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