bug-binutils
[Top][All Lists]
Advanced

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

[Bug ld/21368] how to succesfully build program in MinGW without this in


From: nickc at redhat dot com
Subject: [Bug ld/21368] how to succesfully build program in MinGW without this interrupting
Date: Tue, 11 Apr 2017 08:19:12 +0000

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

Nick Clifton <nickc at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2017-04-11
           Assignee|unassigned at sourceware dot org   |nickc at redhat dot com
     Ever confirmed|0                           |1

--- Comment #3 from Nick Clifton <nickc at redhat dot com> ---
Created attachment 9981
  --> https://sourceware.org/bugzilla/attachment.cgi?id=9981&action=edit
Proposed patch

Hi Budi,

> on Windows 64bit by loading the source from Github, then after completing
> all Msys2 & Mingw64,

A ha!  I think that this is the clue.  The mingw64 version of the linker does
not support the --large-address-aware command line option because it is already
large address aware.  Ie you do not need an option to turn it on, and, more
significantly, you cannot use --disable-large-address-aware to turn it off.

So... the problem is with the how your build is being configured.  Something is
addding the --large-address-aware option to the linker command line, when it
really should not.

I know how difficult it can be to track down and fix build configuration
problems however, so as an alternative I am uploading a small patch for you to
try out.  (Assuming that you are able to build your own version of the linker).
 This patch makes the mingw64 silently accept the --large-address-aware option.
 It does not do anything - there is nothing to be done - but at least now the
linker will not complain about an unrecognised option.

If you are able, please give this patch a test and let me know if it solves the
problem for you.  Alternatively you could track down the problem in your
configuration system and fix that.

Cheers
  Nick

-- 
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]