[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe

2017-02-23 Thread nickc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880 Nick Clifton changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe

2017-02-22 Thread mati865 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880 --- Comment #18 from mati865 at gmail dot com --- Nick I applied https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commitdiff;h=ec8f76882145c71bef81a9cadf0bf51ff9fa5b35 on top of 2.27 binutils and cannot reproduce issue anymore.

[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe

2017-02-22 Thread nickc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880 --- Comment #17 from Nick Clifton --- Hi Guys, (In reply to Eduard Braun from comment #15) > > Setting status to resolved/fixed. > > I don't think this is merged yet! > There's only a patch MINGW-packages, if this works out it should be fixed

[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe

2017-02-21 Thread vsz.bugzilla at emailuser dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880 vsz.bugzilla at emailuser dot net changed: What|Removed |Added Status|RESOLVED|ASSIGNED

[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe

2017-02-21 Thread eduard.braun2 at gmx dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880 --- Comment #15 from Eduard Braun --- > Setting status to resolved/fixed. I don't think this is merged yet! There's only a patch MINGW-packages, if this works out it should be fixed upstream!

[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe

2017-02-21 Thread vsz.bugzilla at emailuser dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880 vsz.bugzilla at emailuser dot net changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe

2017-02-21 Thread vsz.bugzilla at emailuser dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880 --- Comment #13 from vsz.bugzilla at emailuser dot net --- Repeating the minimal tests with MSYS2 `mingw-w64-{i686,x86_64}-binutils-2.27-4-any` (the build that includes the proposed patch), it seems the problem is now fixed for both 32-bit and

[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe

2017-02-21 Thread mati865 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880 mati865 at gmail dot com changed: What|Removed |Added CC||mati865 at gmail dot com ---

[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe

2016-07-13 Thread vsz.bugzilla at emailuser dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880 --- Comment #11 from vsz.bugzilla at emailuser dot net --- Thank you, Nick. I'd be glad to make tests with a binary pre-built using your patches, but building binutils from source myself, appears to be a too long shot at this point. Is there

[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe

2016-07-13 Thread nickc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880 --- Comment #10 from Nick Clifton --- Created attachment 38885 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38885=edit Proposed patch

[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe

2016-07-13 Thread nickc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880 Nick Clifton changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe

2016-07-12 Thread vsz.bugzilla at emailuser dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880 --- Comment #8 from vsz.bugzilla at emailuser dot net --- And the link command output: ``` Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=C:/msys64/mingw32/bin/../lib/gcc/i686-w64-mingw32/5.4.0/lto-wrapper.exe Target: i686-w64-mingw32

[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe

2016-07-12 Thread vsz.bugzilla at emailuser dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880 --- Comment #7 from vsz.bugzilla at emailuser dot net --- Created attachment 38883 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38883=edit Test case #1 Attached a test case that includes all referred sources, generated .o binaries, and

[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe

2016-07-12 Thread nickc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880 --- Comment #6 from Nick Clifton --- (In reply to vsz.bugzilla from comment #5) > You may find a self-contained example under the GitHub link included in the > original report. Direct link: Unfortunately I do not have a MYSY2 installation, or

[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe

2016-07-11 Thread vsz.bugzilla at emailuser dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880 --- Comment #5 from vsz.bugzilla at emailuser dot net --- You may find a self-contained example under the GitHub link included in the original report. Direct link: https://github.com/Alexpux/MSYS2-packages/issues/454#issuecomment-186433276

[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe

2016-07-11 Thread nickc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880 --- Comment #4 from Nick Clifton --- (In reply to Boris Kolpackov from comment #3) > I see this is not the latest generally, but it is the latest available from > the MSYS2 repositories. The last commit here says 2.26 is still no usable: It is

[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe

2016-07-11 Thread boris at kolpackov dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880 --- Comment #3 from Boris Kolpackov --- Ok, I've added support for embedding custom manifests in build2. The resulting .exe's work as expected: custom manifest is used instead of (or in addition to) the default one. However, with grep I can

[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe

2016-07-11 Thread nickc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880 Nick Clifton changed: What|Removed |Added CC||nickc at gcc dot gnu.org --- Comment #2

[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe

2016-07-09 Thread boris at kolpackov dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880 Boris Kolpackov changed: What|Removed |Added CC||boris at kolpackov dot net ---