Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Message-ID: <8D00C32549556B4E977F81DBC24E985D1B1BA5@crtsmail1.technol_exch.corp.riotinto.org> From: "Billinghurst, David (CRTS)" To: "'cygwin-apps AT cygwin DOT com'" Subject: RE: dejagnu-1.4.1 packaging in progress Date: Wed, 25 Jul 2001 00:40:01 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Note-from-DJ: This may be spam My objective is to be able to test gcc-3 on cygwin with the official cygwin dejagnu. I will (try and) do whatever is needed to acheive this result. Some questions: Is there an easy way to identify the "local cygwin hacks"? For example, do you know of a dejagnu version that is a common predecessor of both gnu dejagnu-1.4.1 and the dejagnu from sources.redhat.com? (or do I just diff source trees?) Is there some performance spec for cygwin dejagnu to meet? For example, a cygwin dejagnu must run the xxx and yyy testsuites? > -----Original Message----- > From: Christopher Faylor [SMTP:cgf AT redhat DOT com] > Sent: Wednesday, 25 July 2001 10:24 > To: cygwin-apps AT cygwin DOT com > Subject: Re: dejagnu-1.4.1 packaging in progress > > On Tue, Jul 24, 2001 at 11:44:23PM -0000, Billinghurst, David (CRTS) > wrote: > >Just a note to say I am attempting to package dejagnu-1.4.1 for cygwin. > > > >I have been using my build to test gcc-3 for a few months without any > >problems, and have posted a couple of patches that seem to help. I can't > >build the docs on cygwin, so I have used wget to grab the html version > from > >www.gnu.org > > > >If anyone has a violent objection then let me so I don't waste any time. > > We really have to stick with the dejagnu that comes from > sources.redhat.com. > That has some local cygwin hacks. > > Are you porting those, too? > > cgf