Processing commands for cont...@bugs.debian.org:
> tag 1076933 + upstream fixed-upstream
Bug #1076933 [binutils-mingw-w64-i686] win32-loader: FTBFS: Error: Can't find
IDC_LIST1 (1016) in the custom UI!
Added tag(s) upstream and fixed-upstream.
>
End of message, stopping processing here.
Please c
Control: tag + upstream fixed-upstream
Another short addition:
A patch got discussed and commited upstream:
https://sourceware.org/pipermail/binutils/2024-August/136268.html
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=8c1cd8603443ffeee6e9cc97b738527ea1e2b3e5
On 11.08.2024 11:24, Bernhard Übelacker wrote:
> On Wed, 24 Jul 2024 12:50:23 +0200 Santiago Vila wrote:
>> Package: src:win32-loader
>> Version: 0.10.6
>> Severity: serious
>> Tags: ftbfs
>
>> During a rebuild of all packages in unstable, your package failed to build:
>
>> i686-w64-mingw32-as -
But I am not completely sure if the generated instdlg.o
is valid and expected, and nsis needs to be able to handle it.
Or GNU assembler should really generate object files in the old layout?
Just a short addition:
If GNU assembler and nsis is found to be working as expected
and there exists no
On Wed, 24 Jul 2024 12:50:23 +0200 Santiago Vila wrote:
Package: src:win32-loader
Version: 0.10.6
Severity: serious
Tags: ftbfs
During a rebuild of all packages in unstable, your package failed to build:
i686-w64-mingw32-as --defsym IMAGE_BASE=0x40 -march=i486 -o instdlg.o
/<>/helper
Package: src:win32-loader
Version: 0.10.6
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dpkg-query: no package
6 matches
Mail list logo
