X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 4 Mar 2009 16:29:55 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: [1.7] rebaseall doesn't solve the problem Message-ID: <20090304152955.GE10046@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20090228104337 DOT GG19887 AT calimero DOT vinschen DOT de> <49A986B4 DOT 2080501 AT cwilson DOT fastmail DOT fm> <20090228201625 DOT GA8503 AT calimero DOT vinschen DOT de> <49A9AA0C DOT 9020904 AT cwilson DOT fastmail DOT fm> <20090301102035 DOT GB10046 AT calimero DOT vinschen DOT de> <49AE18D8 DOT 3010009 AT cwilson DOT fastmail DOT fm> <49AE191D DOT 2000307 AT cwilson DOT fastmail DOT fm> <20090304084923 DOT GA10046 AT calimero DOT vinschen DOT de> <20090304111849 DOT GB10046 AT calimero DOT vinschen DOT de> <49AE9742 DOT 4070108 AT cwilson DOT fastmail DOT fm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49AE9742.4070108@cwilson.fastmail.fm> User-Agent: Mutt/1.5.19 (2009-02-20) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Mar 4 09:59, Charles Wilson wrote: > Corinna Vinschen wrote: > > [...] > > - I called "./peflags -t 1 /bin/bash" > > But it seems that the rebase package itself, when built, must be sure to > mark peflags.exe as tsaware before packaging it for distribution, > regardless of which ld.exe is used. Just in case -- otherwise the poor > TS user won't be able to run peflags to fix everything else? Well, my peflags.exe was not TS-aware and worked on TS. The bad joke is that some applications get broken by tsappcmp.dll and some not. I don't see any pattern. The below list (bash, ssh, grep, gdb, mkpasswd, mkgroup) is what I found to get screwed up, other stuff like ash, gawk, ls, nm, peflags, work fine. > > So it seems that setting the TS-aware flag for all applications by > > default is the way to go, same as in Visual C++. > > Makes sense. > > > Unfortunately that doesn't help us with existing packages in the distro, > > only for new ones, but at least we now have the peflags tool for these > > cases. > > Well, we will soon. There's still a few things to deal with. > 1) code audit. I'd appreciate a thorough review of the code before > recommending that people use this tool on every app in their > installation. I know, no warranty express or implied, We're Just Mean, > and You Get To Keep The Pieces, but still... Well, I had a few tiny problems: - VERSION wasn't defined for some reason. - Just for kicks, try `peflags --show-image-characteristics=tsaware /bin/bash' (note: tsaware is a dll-characteristic, not an image-characteristic...) - Stuff like `./peflags.exe --show-dll-characteristics=tsaware' prints nothing at all. I guess it should print a help message due to a missing parameter instead. - peflags --help is missing linebreaks (line 1004 is missing a backslash > 2) peflagsall > 3) I'd like to make sure that the interface to peflags and the new > option(s) to ld are the same or very similar. Once Dave posts his patch > for ld to the binutils list, I'm sure there will be much bike-shedding > about the name of the options, and perhaps discussion about the > implementation. I'd like to wait for ld CVS to be updated with Dave's > eventual contribution after those issues are resolved, and then make > whatever changes to peflags seem appropriate before releasing the tool > "officially". Makes sense. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/