bug-binutils
[Top][All Lists]
Advanced

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

[Bug ld/16790] [cygwin|mingw] ld -v creates a.exe


From: corinna at vinschen dot de
Subject: [Bug ld/16790] [cygwin|mingw] ld -v creates a.exe
Date: Mon, 07 Apr 2014 16:13:11 +0000

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

--- Comment #8 from Corinna Vinschen <corinna at vinschen dot de> ---
(In reply to Nick Clifton from comment #7)

Hi Nick,

> Hi Corinna,
> 
> > After some discussion with Jon_Y and Yaakov on IRC, I'm pretty much ok
> > with moving the default-manifest handling to GCC.
> 
> Excellent! :-)
> 
> > I'm just wondering if the default-manifest shouldn't then be made
> > into its own package, independent of binutils and GCC, so that we
> > can update the default manifest if a new Windows comes out, without
> > having to update binutils or GCC packages as well.
> 
> I guess that this could happen,  Although maybe it could become part of 
> the Cygwin and MinGW projects instead ?  I assume that they are the only 
> ones that need the default manifest.  Hmm, that does mean keeping two 
> copies of the manifest in sync in different projects, which is not 
> ideal.  So maybe a separate project would be better.  How does one go 
> about creating a new project anyway ?

Easy:  I'll create a new cygwin-apps project in the cygwin-apps CVS
       repo on sourceware called "windows-default-manifest" od some
       such, and I will create a Cygwin package from there.  I put
       it under a freeware license so everybody who wants to pick it
       up is free to do so.  I'll keep it up-to-date as far as new
       Windows version come along.

> > If we do that, GCC would have to handle three situations:
> >
> > - The default-manifest.o file doesn't exist in the search path.
> >    Don't even try to add it to the command line.
> 
> Should GCC issue a warning in this case.  (Assuming that it would want 
> to add the default manifest to the linker command line if it could be 
> found).

>From my point of view, no warning should be issued.  It's not a crucial
problem at all.  If it's missing, the executable still works, usually.

> > - The manifest file exists, the -shared option is given.
> >    Don't add default-manifest.o to the command line.
>  >
> > - The manifest file exists, the -shared option is not given.
> >    Append default-manifest.o to the command line.
> >
> > Will that work?
> 
> Yes.  Should be quite straightforward.

Sounds good!


Thanks,
Corinna

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