Bug 1175542 - Building NASM with mingw-gcc fails in a strange manner
Summary: Building NASM with mingw-gcc fails in a strange manner
Alias: None
Product: Fedora
Classification: Fedora
Component: mingw-gcc
Version: 20
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Erik van Pienbroek
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2014-12-18 01:22 UTC by H. Peter Anvin
Modified: 2016-03-17 23:41 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-06-30 01:15:07 UTC
Type: Bug
hpa: needinfo-

Attachments (Terms of Use)

Description H. Peter Anvin 2014-12-18 01:22:25 UTC
Description of problem:
Building NASM 2.11.07 (or from git) with i686-w63-mingw32 fails with a bunch of duplicate symbol errors.

Removing -std=c99 from the command line seems to make it work, but I have not been able to reduce it to a smaller example.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Get NASM 2.11.07 source code.
2. ./autogen.sh
3. ./configure --host=i686-w64-mingw32
4. make

Actual results:
Build failure with a bunch of strange symbol errors.

Expected results:
Executables produced.

Additional info:

Comment 1 Erik van Pienbroek 2014-12-18 06:25:25 UTC
What errors are you getting and what version of mingw32-headers/mingw32-crt are you using?
Did you also try to use the latest mingw32-{gcc,headers,crt,winpthreads} from rawhide?

Comment 2 Fedora End Of Life 2015-05-29 13:31:21 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2015-06-30 01:15:07 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 H. Peter Anvin 2016-03-17 23:41:58 UTC
Verified that this is *not* an issue on current F23.

Note You need to log in before you can comment on or make changes to this bug.