[Bug binutils/19405] nios2 binutils assertion fail at elf32-nios2.c:1038

[romain.naour at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=19405

romain.naour at gmail dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |romain.naour at gmail dot com

--- Comment #7 from romain.naour at gmail dot com ---
Hi Nick, Thomas,

Thanks for your patch!
I tried it over binutils 2.26 release which is currently broken for nios2
toolchain.

First we need to backport [1] to be able to build glibc.
Then I applied your patch and build gtkmm3 package.
Also the same issue with qt (4.8.7) is fixed [2].

But not for imagemagick package which initially failed with [3] and now fail
with:

  CC       magick/magick_libMagickCore_6_Q16_la-pixel.lo
/tmp/ccXCSISE.s: Assembler messages:
/tmp/ccXCSISE.s:13821: Error: r31 cannot be used with jmp; use ret instead
/tmp/ccXCSISE.s:14446: Error: r31 cannot be used with jmp; use ret instead
Makefile:8776: recipe for target
'magick/magick_libMagickCore_6_Q16_la-pixel.lo' failed
make[3]: *** [magick/magick_libMagickCore_6_Q16_la-pixel.lo] Error 1

I wanted to let you know this issue.
It's ok to disable imagemagick for now.

Binutils 2.26 is not upstream yet, I pushed a branch in github [4] if you want
to try using this config:

$ cat > .config <<EOF
BR2_nios2=y
BR2_COMPILER_PARANOID_UNSAFE_PATH=y
BR2_GLIBC_VERSION_2_22=y
BR2_BINUTILS_VERSION_2_26_X=y
BR2_GCC_VERSION_5_X=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_PACKAGE_IMAGEMAGICK=y
EOF

Best regards,
Romain

[1]
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commitdiff;h=a7be2893a6449e64fe6cfcdd8700b0a367a69f19

[2]
http://autobuild.buildroot.net/results/59f/59fdd94bfaf4f6fb7367f5b2f0b56e2acdd371c7/build-end.log

[3]
http://autobuild.buildroot.net/results/0bf/0bf3a2a284b7d4712ab1530562d3b8164fc75e88/build-end.log

[4] https://github.com/RomainNaour/buildroot/tree/nios2-binutils

-- 
You are receiving this mail because:
You are on the CC list for the bug.