public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "filip.zyzniewski at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug ports/12097] New: glibc is unbuildable on an EABI ARMv4 system.
Date: Tue, 05 Oct 2010 18:00:00 -0000 [thread overview]
Message-ID: <bug-12097-131@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=12097
Summary: glibc is unbuildable on an EABI ARMv4 system.
Product: glibc
Version: 2.12
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: ports
AssignedTo: roland@gnu.org
ReportedBy: filip.zyzniewski@gmail.com
I am one of the developers of jlime (http://www.jlime.org). I was
trying to build an userland for the HP Jornada 720 (SA-1110 based
machine) today and I have noticed that it won't build. It fails when
building eglibc with the following error message:
=========================================================
arm-oe-linux-gnueabi-gcc -march=armv4 -mtune=strongarm
-mthumb-interwork -mno-thumb
../ports/sysdeps/unix/sysv/linux/arm/eabi/libc-do-syscall.S -c
-I../include
-I/home/users/filip.zyzniewski/build/tmp/work/armv4-oe-linux-gnueabi/eglibc-initial-2.12-r14.5+svnr11306/build-arm-oe-linux-gnueabi/csu
@/home/users/filip.zyzniewski/build/tmp/work/armv4-oe-linux-gnueabi/eglibc-initial-2.12-r14.5+svnr11306/build-arm-oe-linux-gnueabi/includes
-I.. -I../libio -I. -D_LIBC_REENTRANT -include
../include/libc-symbols.h -DHAVE_INITFINI -DASSEMBLER
-I/home/users/filip.zyzniewski/build/tmp/work/armv4-oe-linux-gnueabi/eglibc-initial-2.12-r14.5+svnr11306/build-arm-oe-linux-gnueabi/csu/.
-Wa,--noexecstack -o
/home/users/filip.zyzniewski/build/tmp/work/armv4-oe-linux-gnueabi/eglibc-initial-2.12-r14.5+svnr11306/build-arm-oe-linux-gnueabi/csu/libc-do-syscall.o
-MD -MP -MF
/home/users/filip.zyzniewski/build/tmp/work/armv4-oe-linux-gnueabi/eglibc-initial-2.12-r14.5+svnr11306/build-arm-oe-linux-gnueabi/csu/libc-do-syscall.o.dt
-MT
/home/users/filip.zyzniewski/build/tmp/work/armv4-oe-linux-gnueabi/eglibc-initial-2.12-r14.5+svnr11306/build-arm-oe-linux-gnueabi/csu/libc-do-syscall.o
../ports/sysdeps/unix/sysv/linux/arm/eabi/libc-do-syscall.S: Assembler
messages:
../ports/sysdeps/unix/sysv/linux/arm/eabi/libc-do-syscall.S:28: Error:
selected processor does not support THUMB opcodes
../ports/sysdeps/unix/sysv/linux/arm/eabi/libc-do-syscall.S:34: Error:
selected processor does not support `push {r7,lr}'
../ports/sysdeps/unix/sysv/linux/arm/eabi/libc-do-syscall.S:39: Error:
selected processor does not support `mov r7,ip'
../ports/sysdeps/unix/sysv/linux/arm/eabi/libc-do-syscall.S:40: Error:
selected processor does not support `swi 0x0'
../ports/sysdeps/unix/sysv/linux/arm/eabi/libc-do-syscall.S:41: Error:
selected processor does not support `pop {r7,pc}'
make[2]: ***
[/home/users/filip.zyzniewski/build/tmp/work/armv4-oe-linux-gnueabi/eglibc-initial-2.12-r14.5+svnr11306/build-arm-oe-linux-gnueabi/csu/libc-do-syscall.o]
Error 1
=========================================================
gcc-4.4.2 and binutils-2.18 (or 2.20, I'm not sure) are capable of
creating working EABI executables for ARMv4 processors. THUMB mode
instructions in the file above cause (e)glibc to be unbuildable in
this configuration.
I've tracked this file down
http://repo.or.cz/w/glibc-ports.git/commitdiff/2dcd7ed8fd149a5aefc8c7a7ff041ff389348b4f
and here I am :).
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2010-10-05 18:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 18:00 filip.zyzniewski at gmail dot com [this message]
2010-10-05 18:12 ` [Bug ports/12097] " filip.zyzniewski at gmail dot com
2010-10-05 20:04 ` joseph at codesourcery dot com
2010-10-05 20:24 ` raj.khem at gmail dot com
2010-10-05 20:29 ` raj.khem at gmail dot com
2010-11-03 22:03 ` bryanhundven at gmail dot com
2010-11-03 22:34 ` bryanhundven at gmail dot com
2010-11-03 22:39 ` bryanhundven at gmail dot com
2011-08-03 12:09 ` dbaryshkov at gmail dot com
2012-02-15 22:30 ` jsm28 at gcc dot gnu.org
2014-06-30 7:53 ` fweimer at redhat dot com
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=bug-12097-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.com \
/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).