This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug ports/12354] compiling glibc gives "previous cfi entry not closed" while compiling on ARM
- From: "r.berber at computer dot org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Thu, 08 Sep 2011 00:21:53 +0000
- Subject: [Bug ports/12354] compiling glibc gives "previous cfi entry not closed" while compiling on ARM
- Auto-submitted: auto-generated
- References: <bug-12354-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12354
Rene Berber <r.berber at computer dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |r.berber at computer dot
| |org
--- Comment #5 from Rene Berber <r.berber at computer dot org> 2011-09-08 00:21:53 UTC ---
(In reply to comment #4)
> I think you are making things much more complicated than necessary. It
> seems more likely that all that's needed is adding END calls to match the
> ENTRY ones in sysdeps/unix/sysv/linux/arm/sigrestorer.S. Note that
> old-ABI has been essentially unmaintained for a long time now; I strongly
> recommend moving to EABI. sysdeps/unix/sysv/linux/arm/eabi/sigrestorer.S
> has the END calls and the file you reference should not be used at all in
> an EABI build.
I stumbled on the same bug, with glibc 2.12.2 and glibc-ports 2.12.1 (there is
no corresponding release), and using gcc 4.5.3 and binutils 2.21.1.
But the interesting point is that both Michel and me are using gnueabi, which
is not the old abi (for instance 'objdump -x as' | grep private' returns
"private flags = 4000002: [Version4 EABI] [has entry point]").
The bug seems to be what you point out, somehow the old abi is used.
Could be a bug in the ports add-on.
--
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.