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:[EMAIL PROTECTED]]
> Sent: Wednesday, 25 July 2001 10:24
> To: [EMAIL PROTECTED]
> 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
