Bug 405355 – cross-arm-unknown-linux-gnu/glibc-2.13-r4 - Assembler messages: ../ports/sysdeps/unix/sysv/linux/arm/sigrestorer.S:30: Error: previous CFI entry not closed (missing .cfi_endproc)

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Jude Pereira 2012-02-23 02:45:46 UTC]

I'm building an ARM compiler, using crossdev, with the stable versions of everything.
crossdev --stage4 --stable --show-fail-log --target arm

It fails at glibc, attached are the info.log and the build log.
I've tried with other versions of glibc as well, they all seem to fail for me.

Anyone seen this before?

The main error is this:
make[2]: *** [/media/multimedia/build/portage/cross-arm-unknown-linux-gnu/glibc-2.13-r4/work/build-default-arm-unknown-linux-gnu-nptl/signal/sigrestorer.os] Error 1


Reproducible: Always

Steps to Reproduce:
1. On 64bit gentoo, execute crossdev --stage4 --stable --show-fail-log --target arm
Actual Results:  
glibc does not compile

Expected Results:  
glibc should compile just right.

[Comment 1 Jude Pereira 2012-02-23 02:47:25 UTC]

Created attachment 302927 [details]
/var/log/portage/cross-arm-unknown-linux-gnu-info.log

[Comment 2 Jude Pereira 2012-02-23 02:47:47 UTC]

Created attachment 302929 [details]
/var/log/portage/cross-arm-unknown-linux-gnu-glibc.log

[Comment 3 Jude Pereira 2012-02-23 03:17:49 UTC]

rm -rf /.config seemed to do some magic, it gave me a more better debuggable error this time:

../ports/sysdeps/unix/sysv/linux/arm/sigrestorer.S: Assembler messages:
../ports/sysdeps/unix/sysv/linux/arm/sigrestorer.S:30: Error: previous CFI entry not closed (missing .cfi_endproc)
/media/multimedia/build/portage/cross-arm-unknown-linux-gnu/glibc-2.13-r4/temp/ccZ576E6.s: Error: open CFI at the end of file; missing .cfi_endproc directive
make[2]: *** [/media/multimedia/build/portage/cross-arm-unknown-linux-gnu/glibc-2.13-r4/work/build-default-arm-unknown-linux-gnu-nptl/signal/sigrestorer.os] Error 1


geneswitch on #gentoo pointed me to http://sourceware.org/ml/libc-ports/2012-01/msg00003.html

[Comment 4 Jude Pereira 2012-02-23 03:34:41 UTC]

Failed yet again with vapier's patch:

../sysdeps/unix/syscall-template.S: Assembler messages:
../sysdeps/unix/syscall-template.S:82: Error: CFI instruction used without previous .cfi_startproc
../sysdeps/unix/syscall-template.S:82: Error: CFI instruction used without previous .cfi_startproc
../sysdeps/unix/syscall-template.S:82: Error: CFI instruction used without previous .cfi_startproc
../sysdeps/unix/syscall-template.S:82: Error: CFI instruction used without previous .cfi_startproc

[Comment 5 SpanKY 2012-02-23 05:27:16 UTC]

already been fixed in newer versions of glibc

[Comment 6 Ed Watson 2012-02-23 12:52:51 UTC]

Which version is it fixed in?
I just ran 
crossdev --stage4 --stable --show-fail-log --target arm --l 2.14
and got the same error. 

Thanks

(In reply to comment #5)
> already been fixed in newer versions of glibc

[Comment 7 SpanKY 2012-02-24 21:59:52 UTC]

it's fixed in 2.14.1

alternatively, use EABI instead of OABI

[Comment 8 Jude Pereira 2012-02-25 01:13:52 UTC]

2.14.1-r2 failed with the same issue, let me try changing ABIs

[Comment 9 Jude Pereira 2012-02-25 01:33:05 UTC]

Created attachment 303113 [details]
build log for glibc 2.14.1-r2 with EABI - still fails

EABI fails too.
Here's a build log for glibc 2.14.1-r2


crossdev command:
crossdev --stage4 --stable --show-fail-log --target arm --abis EABI

[Comment 10 SpanKY 2012-02-26 17:29:43 UTC]

the EABI failure is completely different; please file a new bug

OABI builds fine for me:
cross-arm-unknown-linux-gnu/binutils-2.22-r1
cross-arm-unknown-linux-gnu/gcc-4.5.3-r2
cross-arm-unknown-linux-gnu/glibc-2.14.1-r2
cross-arm-unknown-linux-gnu/linux-headers-3.1

[Comment 11 SpanKY 2012-02-26 18:36:49 UTC]

actually, don't file a bug.  if you want to use eabi, you have to set your tuple accordingly.  arm-linux-gnueabi.

[Comment 12 Jude Pereira 2012-02-27 02:49:31 UTC]

Using your versions of the packages for OABI failed, I used the EABI tuple, and it worked. The OABI issue still needs to be fixed, I received the same efi errors.

[Comment 13 SpanKY 2012-04-10 16:19:46 UTC]

*** Bug 411263 has been marked as a duplicate of this bug. ***