From: "Benoît Thébaudeau" <benoit.thebaudeau@advansee.com>
To: "Christian Möller" <moeller@ap-microcomputer.de>
Cc: crossgcc@sourceware.org
Subject: Re: Glibc Build locals
Date: Thu, 16 Feb 2012 12:50:00 -0000 [thread overview]
Message-ID: <3dd556ab-a85f-4cd2-9a82-b3da1905312d@zose-store-12> (raw)
In-Reply-To: <4F3CC611.6080306@ap-microcomputer.de>
Hi Christian, all,
Can you retry with CT-NG default-e0d70cf2b396 and/or eglibc 2.13? I've already tested that CT-NG default-e0d70cf2b396 with eglibc 2.13 and locales support enabled works for ARM targets and Ubuntu 11.10 build machines, so if you use that CT-NG/eglibc combination, we'll know more accurately where your issue comes from.
Benoît
----- Original Message -----
> From: "Christian Möller" <moeller@ap-microcomputer.de>
> To: crossgcc@sourceware.org
> Sent: Thursday, February 16, 2012 10:02:09 AM
> Subject: Glibc Build locals
>
> Dear List,
> i try to build a toolchain for an geode target on fedora 16.
> I need glibc and full locale support.
> With "build and install locales" enabled the build failed.
>
> [ALL ] /tmp/ccGXC39V.s: Assembler messages:
> [ALL ] /tmp/ccGXC39V.s: Error: open CFI at the end of file;
> missing
> .cfi_endproc directive
> [ALL ] /tmp/ccGXC39V.s: Error: open CFI at the end of file;
> missing
> .cfi_endproc directive
> [ERROR] make[3]: ***
> [/home/moeller/Entwicklung/crosstool-ng/.build/i586-unknown-linux-gnu/build/build-localedef/csu/crti.o]
> Error 1
> [ALL ] make[3]: *** Waiting for unfinished jobs....
> [ALL ] /tmp/ccNqlW5V.s: Assembler messages:
> [ALL ] /tmp/ccNqlW5V.s:33: Error: CFI instruction used without
> previous .cfi_startproc
> [ALL ] /tmp/ccNqlW5V.s:35: Error: .cfi_endproc without
> corresponding
> .cfi_startproc
> [ALL ] /tmp/ccNqlW5V.s:48: Error: CFI instruction used without
> previous .cfi_startproc
> [ALL ] /tmp/ccNqlW5V.s:50: Error: CFI instruction used without
> previous .cfi_startproc
> [ALL ] /tmp/ccNqlW5V.s:51: Error: CFI instruction used without
> previous .cfi_startproc
> [ALL ] /tmp/ccNqlW5V.s:53: Error: .cfi_endproc without
> corresponding
> .cfi_startproc
> [ERROR] make[3]: ***
> [/home/moeller/Entwicklung/crosstool-ng/.build/i586-unknown-linux-gnu/build/build-localedef/csu/crtn.o]
> Error 1
> [ALL ] make[3]: Leaving directory
> `/home/moeller/Entwicklung/crosstool-ng/.build/src/glibc-2.9/csu'
> [ERROR] make[2]: *** [csu/subdir_lib] Error 2
> [ALL ] make[2]: Leaving directory
> `/home/moeller/Entwicklung/crosstool-ng/.build/src/glibc-2.9'
> [ERROR] make[1]: *** [all] Error 2
> [ALL ] make[1]: Leaving directory
> `/home/moeller/Entwicklung/crosstool-ng/.build/i586-unknown-linux-gnu/build/build-localedef'
> [ERROR]
> [ERROR] >>
> [ERROR] >> Build failed in step 'Installing C library'
> [ERROR] >> called in step '(top-level)'
> [ERROR] >>
> [ERROR] >> Error happened in: CT_DoExecLog[scripts/functions@172]
> [ERROR] >> called from:
> do_libc_locales[scripts/build/libc/glibc.sh@116]
> [ERROR] >> called from:
> do_libc_backend_once[scripts/build/libc/glibc-eglibc.sh-common@464]
> [ERROR] >> called from:
> do_libc_backend[scripts/build/libc/glibc-eglibc.sh-common@143]
> [ERROR] >> called from:
> do_libc[scripts/build/libc/glibc-eglibc.sh-common@65]
> [ERROR] >> called from: main[scripts/crosstool-NG.sh@597]
> [ERROR] >>
> [ERROR] >> For more info on this error, look at the file:
> 'build.log'
> [ERROR] >> There is a list of known issues, some with workarounds,
> in:
> [ERROR] >>
> '/usr/local/share/doc/crosstool-ng/ct-ng.hg+default-369e2fbe9010/B -
> Known issues.txt'
> [ERROR]
> [ERROR] (elapsed: 7:38.96)
>
> Any help is welcome.
> Christian
>
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2012-02-16 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 9:03 Christian Möller
2012-02-16 12:50 ` Benoît Thébaudeau [this message]
[not found] <4F476650.20701@ap-microcomputer.de>
2012-02-24 12:14 ` Benoît Thébaudeau
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=3dd556ab-a85f-4cd2-9a82-b3da1905312d@zose-store-12 \
--to=benoit.thebaudeau@advansee.com \
--cc=crossgcc@sourceware.org \
--cc=moeller@ap-microcomputer.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).