bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/21233] New: Internal error, /usr/bin/ld: BFD (GNU Binutils


From: costamagnagianfranco at yahoo dot it
Subject: [Bug binutils/21233] New: Internal error, /usr/bin/ld: BFD (GNU Binutils for Debian) 2.28 assertion fail ../../bfd/elfxx-mips.c:3861
Date: Wed, 08 Mar 2017 09:38:40 +0000

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

            Bug ID: 21233
           Summary: Internal error, /usr/bin/ld: BFD (GNU Binutils for
                    Debian) 2.28 assertion fail
                    ../../bfd/elfxx-mips.c:3861
           Product: binutils
           Version: 2.28
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: binutils
          Assignee: unassigned at sourceware dot org
          Reporter: costamagnagianfranco at yahoo dot it
  Target Milestone: ---

Hello, I suspect the changes below introduced a regression in the linker for
mips architecture, now we can't build ghc anymore in Debian

+2017-02-13  Maciej W. Rozycki  <address@hidden>
+
+       * elfxx-mips.c (mips_elf_hash_sort_data): Add
+       `max_local_dynindx'.
+       (mips_elf_sort_hash_table): Handle it.
+       (mips_elf_sort_hash_table_f) <GGA_NONE>: For forced local
+       symbols bump up `max_local_dynindx' rather than
+       `max_non_got_dynindx'.
+
+2017-02-13  Maciej W. Rozycki  <address@hidden>
+
+       * elfxx-mips.c (mips_elf_hash_sort_data): Convert the
+       `min_got_dynindx', `max_unref_got_dynindx' and
+       `max_non_got_dynindx' members to the `bfd_size_type' data type.
+       (mips_elf_sort_hash_table): Adjust accordingly.

this happens on mips, mipsel, and mips64el
You can see build logs here
https://buildd.debian.org/status/fetch.php?pkg=ghc&arch=mips&ver=8.0.1-17%2Bb1&stamp=1488954233&raw=0
https://buildd.debian.org/status/package.php?p=ghc&suite=unstable

I hope I can avoid to have to recompile the whole ghc package in a porterbox,
but in case, please ask and I'll provide whatever can help in debug this issue

thanks

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


reply via email to

[Prev in Thread] Current Thread [Next in Thread]