From: "jozef maslik" <jmaslik@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] crossdev failed during building uclibc
Date: Sat, 24 Feb 2007 23:04:24 +0100 [thread overview]
Message-ID: <b027306a0702241404g229120b7mebca0b82aee46413@mail.gmail.com> (raw)
In-Reply-To: <200702241820.25692.ladmanj@volny.cz>
Hello !
Have you read /var/log/portage/cross-mips-pc-linux-uclibc-uclibc.log ?
If you have not read it, please read it and try:
You do not have a codesets.txt file. Please create this
file in the extra/locale directory by running something like:
find /var/tmp/cross/mips-pc-linux-uclibc/portage/cross-mips-pc-linux-uclibc/uclibc-0.9.28.1/work/uClibc-0.9.28.1/extra/locale/charmaps
-name "*.pairs" > \
/var/tmp/cross/mips-pc-linux-uclibc/portage/cross-mips-pc-linux-uclibc/uclibc-0.9.28.1/work/uClibc-0.9.28.1/extra/locale/codesets.txt
and then edit that file to disable/enable the codesets you wish to support.
make: *** [codesets.txt] Error 1
... and mail again... :)
On 2/24/07, Jakub Ladman <ladmanj@volny.cz> wrote:
> Hi there
> Me and my friend have both encountered this problem:
>
> hovado ~ # crossdev --g 3.4.6-r2 --k 2.4.26-r1 -t mips-pc-linux-uclibc
> --------------------------------------------------------------------------------
> * Host Portage ARCH: x86
> * Target Portage ARCH: mips
> * Target System: mips-pc-linux-uclibc
> * Stage: 4 (C/C++ compiler)
>
> * binutils: binutils-[latest]
> * gcc: gcc-3.4.6-r2
> * headers: mips-headers-2.4.26-r1
> * libc: uclibc-[latest]
>
> * PORTDIR_OVERLAY: /usr/local/portage
> * PORT_LOGDIR: /var/log/portage
> * PKGDIR: /usr/portage/packages/cross/mips-pc-linux-uclibc
> * PORTAGE_TMPDIR: /var/tmp/cross/mips-pc-linux-uclibc
> _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ -
> * Forcing the latest versions of binutils-config/gcc-config ... [
> ok ]
> * Log: /var/log/portage/cross-mips-pc-linux-uclibc-binutils.log
> * Emerging cross-binutils ... [
> ok ]
> * Log: /var/log/portage/cross-mips-pc-linux-uclibc-gcc-stage1.log
> * Emerging cross-gcc-stage1 ... [
> ok ]
> * Log: /var/log/portage/cross-mips-pc-linux-uclibc-mips-headers.log
> * Emerging cross-mips-headers ... [
> ok ]
> * Log: /var/log/portage/cross-mips-pc-linux-uclibc-uclibc.log
> * Emerging cross-uclibc ...
>
> * uclibc failed :(
> * If you file a bug, please attach the following logfiles:
> * /var/log/portage/cross-mips-pc-linux-uclibc-info.log
> * /var/log/portage/cross-mips-pc-linux-uclibc-uclibc.log
> hovado ~ #
>
> Do anybody know how to fix it?
>
> There are crossdev logs in attachments.
>
> Thank you.
> Jakub Ladman
>
>
>
--
gentoo-embedded@gentoo.org mailing list
next prev parent reply other threads:[~2007-02-24 22:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-24 17:20 [gentoo-embedded] crossdev failed during building uclibc Jakub Ladman
2007-02-24 22:04 ` jozef maslik [this message]
2007-02-25 10:18 ` Jakub Ladman
2007-02-25 11:14 ` jozef maslik
2007-03-04 18:32 ` Jakub Ladman
2007-02-25 3:46 ` [gentoo-embedded] Embeded Gentoo mentioned in Linux Journal Heath Holcomb
2007-02-25 8:09 ` Wernfried Haas
-- strict thread matches above, loose matches on Subject: below --
2007-03-24 14:52 [gentoo-embedded] crossdev failed during building uclibc ducasse.isidore
2007-03-30 6:24 ` Mike Frysinger
2007-03-24 16:16 ducasse.isidore
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=b027306a0702241404g229120b7mebca0b82aee46413@mail.gmail.com \
--to=jmaslik@gmail.com \
--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