DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=p3Oe4tlQPqeCEsrSaVFxNoev7bqBVZ5lz0dGyNK5LK8UoeghQ5FoB
	bckYqmMNynZfPHHtE6Ab6M9hmXBNEaHC/02tI++iQ2dLwU0kLlt8nxH9/GE7wMSq
	jFRENtiByvmDE5v8ZoRB7pg+kJUx543Io+qfW1+R6QZajiLypEeF/M=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Thu, 13 Mar 2014 20:40:56 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Compiled executables requiring admin rights - different results between MinGW host type
Message-ID: <20140313194056.GI2547@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <E29840B52F804D728672875F0A8D534E@TKsamsung> <20140312184136.GB2547@calimero.vinschen.de> <5321EEE9.6050009@users.sourceforge.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="1Y7d0dPL928TPQbc"
Content-Disposition: inline
In-Reply-To: <5321EEE9.6050009@users.sourceforge.net>
User-Agent: Mutt/1.5.21 (2010-09-15)

--1Y7d0dPL928TPQbc
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mar 13 12:46, Yaakov (Cygwin/X) wrote:
> On 2014-03-12 13:41, Corinna Vinschen wrote:
> >Our maintainers of the mingw-binutls and native binutils package just
> >have to update the packages to the latest from binutils git.  Actually,
> >that reminds me...
> >
> >JonY, ping?  A couple of days ago, Nick Clifton updated binutils for
> >Windows so that every executable, which doesn't provide its own
> >manifest, will get a default manifest.
> [snip]
> >So, if you have a bit of time, it would be nice to get new
> >mingw64-i686-binutils and mingw64-x86_64-binutils packages (as well
> >as a new Cygwin binutils, but cgf already knows about this).
>=20
> Not to mention a new cygwin*-binutils for Cygwin and Fedora.  cgf,
> are you carrying any patches on top of today's 2.24.51 snapshot?
>=20
> Once all the PE-target binutils are updated, I can rip out all the
> manifest-generation code in cygport, right?

In theory, yes.  Given that the default manifest will mark the
executable as "asInvoker", it will remove the requirement to
have all the "asInvoker" manifests alongside patch.exe, install.exe,
install-info.exe, update-mime-database.exe, etc, as soon as the are
rebuilt with the new binutils.

> >Every time a new Windows version is released, we will have to update the
> >default manifest in binutils, too, but that's the price we have to pay
> >for compatibility.  Sigh.
>=20
> A mass rebuild every few years wouldn't hurt; I'd say we're actually
> overdue for one on x86.

Nice idea, but pretty much impossible, I assume.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--1Y7d0dPL928TPQbc
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJTIgnIAAoJEPU2Bp2uRE+gFVUP/2ptOl+LxoZM79qMlLDMyHrf
heBa1ojC4XMbWLt4t/KLoPOU7FuzyjBXj5/nzBBiFSv4JNdDxmPLH8FMWv/+bFEt
YR46OjWBm6EvoHStnAg6FxRWQnND4EIsqCCo4WS2WEH5u6Cj4PREPShoINI18gnj
NF+VC7rNYeCj1rilHl+G7dl1fcob5Q5GtkyJB2gI+W9qpImNHZBeVDOiEEVhbbOS
E4vBpPgW/pilEni/QFrKkknMQNHRaq1lz4RcQVRuvmnyj6UgU9iTKWS1Fubrg1dz
Sesez1E9z0dEraIV6HSc7AwUBF8ljSNf0z0rqW9LkWKUsDKw9p6+XO5KwqlBn9f1
9gru+AOSaTNY0Sh8Bfy/ZQnNP4nNp4ScWl38xoQGgd5Gsqe8ZsR2xeS1yeD9Vw03
ZVI2sy154rcsugSqLm30Ap1GeQ745REv2YrzP/BSzZLQPguD+1QB8uyw1Whvt2Hu
GC4DO0h+fILG98IRZDYrD378dtLW8RGTikWnjFBBBzcuUoTerdddH3uxRKFzkjff
2KCzCf0C1gwV+fNg491QR4ChBGslu+VpzpD5oqSRrCoe4FZyRMiGcTZFmx08NduN
+9r4mMPZE3x6wVTwbYDTiuvTIUVGNRkXH2aGmhJTDsYmWsgQnmJONz64oQUJoq9Y
4k/FE7S+0l/5zKv30XAf
=dCMO
-----END PGP SIGNATURE-----

--1Y7d0dPL928TPQbc--