From: "Andre Rhone" <accolade12@comcast.net>
To: <gentoo-embedded@lists.gentoo.org>
Subject: RE: [gentoo-embedded] configure: error: forced unwind support is required
Date: Thu, 22 Mar 2007 09:34:52 -0400 [thread overview]
Message-ID: <200703221334.l2MDYuJp008678@robin.gentoo.org> (raw)
In-Reply-To: <A215103B7880F64D9CB8E88EF3F9455F0432EE7A@EVS1.tomotherapy.com>
[-- Attachment #1: Type: text/plain, Size: 3368 bytes --]
Try glibc-2.5-r1 and binutils 2.17.50.0.9. You may have to unmask them
first. Also, to protect your system from human error, you may want to do it
in a 32/64bit chrooted env.
http://www.gentoo.org/proj/en/base/amd64/howtos/index.xml?part=1
<http://www.gentoo.org/proj/en/base/amd64/howtos/index.xml?part=1&chap=2>
&chap=2
(e.g.) USE="-fortran" crossdev-stable --binutils 2.17.50.0.9 --gcc 4.1.2
--libc 2.5-r1 --kernel 2.6.19.2-r2 -t armv5te-softfloat-linux-gnueabi
_____
From: Chuck McKenzie [mailto:cmckenzie@tomotherapy.com]
Sent: Wednesday, March 21, 2007 4:13 PM
To: gentoo-embedded@lists.gentoo.org
Subject: [gentoo-embedded] configure: error: forced unwind support is
required
Hi all,
I'm new to Gentoo embedded and fairly new to Gentoo, so I apologize if I am
missing something obvious. I'm having trouble getting the crossdev toolchain
up and running with a current portage sync. Could someone please point me
in the direction of fixing this?
Here's what I'm seeing:
buildhost ~ # crossdev -t i686-unknown-linux-gnu
----------------------------------------------------------------------------
----------------------------------------------------------------------------
------
* Host Portage ARCH: x86
* Target Portage ARCH: x86
* Target System: i686-unknown-linux-gnu
* Stage: 4 (C/C++ compiler)
* binutils: binutils-[latest]
* gcc: gcc-[latest]
* headers: linux-headers-[latest]
* libc: glibc-[latest]
* PORTDIR_OVERLAY: /usr/local/portage
* PORT_LOGDIR: /var/log/portage
* PKGDIR: /usr/portage/packages/cross/i686-unknown-linux-gnu
* PORTAGE_TMPDIR: /var/tmp/cross/i686-unknown-linux-gnu
_ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _
- ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~
-
* Forcing the latest versions of binutils-config/gcc-config ...
[ ok ]
* Log: /var/log/portage/cross-i686-unknown-linux-gnu-binutils.log
* Emerging cross-binutils ...
[ ok ]
* Log: /var/log/portage/cross-i686-unknown-linux-gnu-gcc-stage1.log
* Emerging cross-gcc-stage1 ...
[ ok ]
* Log: /var/log/portage/cross-i686-unknown-linux-gnu-linux-headers.log
* Emerging cross-linux-headers ...
[ ok ]
* Log: /var/log/portage/cross-i686-unknown-linux-gnu-glibc.log
* Emerging cross-glibc ...
* glibc failed :(
>From /var/log/portage/cross-i686-unknown-linux-gnu-glibc.log
<snip>
checking for forced unwind support... no
configure: error: forced unwind support is required
!!! ERROR: cross-i686-unknown-linux-gnu/glibc-2.5 failed.
Call stack:
ebuild.sh, line 1614: Called dyn_compile
ebuild.sh, line 971: Called qa_call 'src_compile'
environment, line 4123: Called src_compile
glibc-2.5.ebuild, line 1119: Called src_compile
glibc-2.5.ebuild, line 1130: Called toolchain-glibc_src_compile
glibc-2.5.ebuild, line 240: Called glibc_do_configure 'nptl'
glibc-2.5.ebuild, line 900: Called die
!!! failed to configure glibc
!!! If you need support, post the topmost build error, and the call stack if
relevant.
!!! A complete build log is located at
'/var/tmp/cross/i686-unknown-linux-gnu/portage/cross-i686-unknown-linux-gnu/
glibc-2.5/temp/build.log'.
!!! This ebuild is from an overlay: '/usr/local/portage'
[-- Attachment #2: Type: text/html, Size: 9851 bytes --]
next prev parent reply other threads:[~2007-03-22 13:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 20:13 [gentoo-embedded] configure: error: forced unwind support is required Chuck McKenzie
2007-03-22 13:34 ` Andre Rhone [this message]
2007-03-24 7:30 ` Mike Frysinger
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=200703221334.l2MDYuJp008678@robin.gentoo.org \
--to=accolade12@comcast.net \
--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