[Bug binutils/32072] ./dlltool.c:870:27: error: initializer-string for array of 'char' is too long

2024-08-11 Thread jbg...@lug-owl.de
||i686-mingw32crt, ||i686-cygwin CC||jbg...@lug-owl.de -- You are receiving this mail because: You are on the CC list for the bug.

[Bug binutils/32072] New: ./dlltool.c:870:27: error: initializer-string for array of 'char' is too long

2024-08-11 Thread jbg...@lug-owl.de
NCONFIRMED Severity: normal Priority: P2 Component: binutils Assignee: unassigned at sourceware dot org Reporter: jbg...@lug-owl.de Target Milestone: --- Hi! While doing automated builds using a _very_ recent host GCC (gcc (basepoints/gcc-15-2866-g9

[Bug gas/31617] VAX: Check immediates to match expected operand type

2024-04-07 Thread jbg...@lug-owl.de
https://sourceware.org/bugzilla/show_bug.cgi?id=31617 Jan-Benedict Glaw changed: What|Removed |Added CC||jbg...@lug-owl.de -- You are

[Bug gas/31617] VAX: Check immediates to match expected operand type

2024-04-07 Thread jbg...@lug-owl.de
https://sourceware.org/bugzilla/show_bug.cgi?id=31617 Jan-Benedict Glaw changed: What|Removed |Added Target||vax-netbsdelf, vax-linux -- You

[Bug gas/31617] New: VAX: Check immediates to match expected operand type

2024-04-07 Thread jbg...@lug-owl.de
Component: gas Assignee: unassigned at sourceware dot org Reporter: jbg...@lug-owl.de Target Milestone: --- In NetBSD's src/sys/arch/vax/vax/unimpl_emul.S, we had three bogus assembler statements: movq $0f0.0, TMPFRAC2 movd $0f0.0, TMP

[Bug ld/28910] GNU-ld: ARM: Issues when trying to set target output architecture

2023-11-14 Thread jbg...@lug-owl.de
https://sourceware.org/bugzilla/show_bug.cgi?id=28910 --- Comment #26 from Jan-Benedict Glaw --- All mass compilations of Binutils worked as expected. Linux kernel builds are running, but no other regressions (and parisc and sh are fixed.) Thanks! -- You are receiving this mail because: You ar

[Bug ld/28910] GNU-ld: ARM: Issues when trying to set target output architecture

2023-11-13 Thread jbg...@lug-owl.de
https://sourceware.org/bugzilla/show_bug.cgi?id=28910 --- Comment #21 from Jan-Benedict Glaw --- Got two "green": http://toolchain.lug-owl.de/laminar/jobs/linux-parisc-generic-32bit_defconfig/57 http://toolchain.lug-owl.de/laminar/jobs/linux-sh-microdev_defconfig/38 I have not yet tested whethe

[Bug ld/28910] GNU-ld: ARM: Issues when trying to set target output architecture

2023-11-11 Thread jbg...@lug-owl.de
https://sourceware.org/bugzilla/show_bug.cgi?id=28910 Jan-Benedict Glaw changed: What|Removed |Added CC||jbg...@lug-owl.de --- Comment

[Bug ld/30568] --dependency-file includes temporary LTO files

2023-07-06 Thread jbg...@lug-owl.de
https://sourceware.org/bugzilla/show_bug.cgi?id=30568 --- Comment #8 from Jan-Benedict Glaw --- That fixes the intermediate build issue, thanks. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug ld/30568] --dependency-file includes temporary LTO files

2023-07-05 Thread jbg...@lug-owl.de
https://sourceware.org/bugzilla/show_bug.cgi?id=30568 --- Comment #6 from Jan-Benedict Glaw --- Slowly showing up on other builds as well: i686-pc-msdosdjgpp (http://toolchain.lug-owl.de/laminar/jobs/binutils-i686-pc-msdosdjgpp/38) -- You are receiving this mail because: You are on the CC list

[Bug ld/30568] --dependency-file includes temporary LTO files

2023-07-05 Thread jbg...@lug-owl.de
https://sourceware.org/bugzilla/show_bug.cgi?id=30568 Jan-Benedict Glaw changed: What|Removed |Added CC||jbg...@lug-owl.de --- Comment #5

[Bug gas/30197] gas: Error: bad value (sr71k) for default CPU

2023-03-05 Thread jbg...@lug-owl.de
https://sourceware.org/bugzilla/show_bug.cgi?id=30197 Jan-Benedict Glaw changed: What|Removed |Added Target||mipsisa64sr71k-elf Ver

[Bug gas/30197] New: gas: Error: bad value (sr71k) for default CPU

2023-03-05 Thread jbg...@lug-owl.de
Component: gas Assignee: unassigned at sourceware dot org Reporter: jbg...@lug-owl.de Target Milestone: --- Hi! While mass-building toolchains, I came across --target=mipsisa64sr71k-elf. Binutils/gas built and are in $PATH for a GCC build, which fails (full log at http

[Bug gprofng/29987] bfd/archive.c:1447: undefined reference to `filename_ncmp'

2023-01-18 Thread jbg...@lug-owl.de
https://sourceware.org/bugzilla/show_bug.cgi?id=29987 --- Comment #7 from Jan-Benedict Glaw --- Build is currently restored by reverting the initial patch. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug gprofng/29987] bfd/archive.c:1447: undefined reference to `filename_ncmp'

2023-01-17 Thread jbg...@lug-owl.de
https://sourceware.org/bugzilla/show_bug.cgi?id=29987 --- Comment #6 from Jan-Benedict Glaw --- Just ftr: The build-many-glibcs.py script does the equivalent of: /var/cache/git/binutils-gdb/configure '--prefix=/tmp/b/i' \ '--build=x86

[Bug gprofng/29987] bfd/archive.c:1447: undefined reference to `filename_ncmp'

2023-01-17 Thread jbg...@lug-owl.de
https://sourceware.org/bugzilla/show_bug.cgi?id=29987 --- Comment #5 from Jan-Benedict Glaw --- I do regular builds (own build strategy and a hacked build-many-glibcs.py to allow for HEAD versions) and the later started to fail since this commit: /bin/bash ../libtool --tag=CXX --mode=link g++

[Bug gprofng/29987] bfd/archive.c:1447: undefined reference to `filename_ncmp'

2023-01-17 Thread jbg...@lug-owl.de
https://sourceware.org/bugzilla/show_bug.cgi?id=29987 Jan-Benedict Glaw changed: What|Removed |Added CC||jbg...@lug-owl.de -- You are