Since the required fix seemed to be a simple find and replace,
I did it myself: the new patch is at
http://www.cs.utexas.edu/~subbuk/cygwin-ddd-patch.gz
So the new recipe is as follows:
1. cp -r ddd-3.3.8 ddd-3.3.8-orig
2. wget http://www.cs.utexas.edu/~subbuk/cygwin-ddd-patch.gz
gunzip -c cyg
No need. I fixed my local version by hand.
Harold
S Iyer wrote:
Harold, it is Richard's patch not mine. I was only pointing out
that one step in the recipe should be removed - if you move
the gcc/include into ddd/include, then patch gets confused
on those files.
That said, the error is in non-c
Harold, it is Richard's patch not mine. I was only pointing out
that one step in the recipe should be removed - if you move
the gcc/include into ddd/include, then patch gets confused
on those files.
That said, the error is in non-cygwin case, which is why the
whole compilation went through flawles
t; Date: Fri, 05 Dec 2003 17:00:54 -0500
> From: Harold L Hunt II <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: DDD 3.3.8 recipe - was - RE: libtool created import libs brok
> en? was RE: DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault
>
> Subbu,
>
&
Subbu,
The patch is no good. It takes the following:
#ifdef __GNUG__
#pragma implementation "foo.h"
#endif
and turns it into:
#ifdef __GNUG__
#ifndef __CYGWIN__
#pragma implementation
#endif "foo.h"
#endif
Here is an example:
#ifdef __GNUG__
+#ifndef __CYGWIN__
#pragma implementation
-#pragm
Brian,
Brian Ford wrote:
On Fri, 5 Dec 2003, Harold L Hunt II wrote:
Richard Campbell wrote:
Harold L Hunt II wrote:
This is due to the way that the configure script for libiberty is called
in configure.ac:
If I was paying attention, libiberty uses autoconf 2.13 or similar, and the
other pieces
On Fri, 5 Dec 2003, Harold L Hunt II wrote:
> Richard Campbell wrote:
> >Harold L Hunt II wrote:
> >>This is due to the way that the configure script for libiberty is called
> >>in configure.ac:
> >>
> > If I was paying attention, libiberty uses autoconf 2.13 or similar, and the
> > other pieces us
Richard Campbell wrote:
This is due to the way that the configure script for libiberty is called
in configure.ac:
If I was paying attention, libiberty uses autoconf 2.13 or similar, and the
other pieces use 2.5...That's going to be a real pain to set up, I think...
It's just our top-level confi
>This is due to the way that the configure script for libiberty is called
>in configure.ac:
If I was paying attention, libiberty uses autoconf 2.13 or similar, and the
other pieces use 2.5...That's going to be a real pain to set up, I think...
-Richard Campbell.
Subbu,
S Iyer wrote:
Step no 2 (copying the gcc include files) is no longer necessary
as it is subsumed by the diff. So all that needs done to get a
working ddd is:
1. cp -r ddd-3.3.8 ddd-3.3.8-orig
2. wget http://bellsouthpwp.net/u/l/ulvester/iffs.gz
gunzip -c iffs.gz | patch -p0
3. c
Step no 2 (copying the gcc include files) is no longer necessary
as it is subsumed by the diff. So all that needs done to get a
working ddd is:
1. cp -r ddd-3.3.8 ddd-3.3.8-orig
2. wget http://bellsouthpwp.net/u/l/ulvester/iffs.gz
gunzip -c iffs.gz | patch -p0
3. cd ddd-3.3.8 && bash ./
Resend - got denied because of attachment size, so I've uploaded my diffs to
a web page.
Ok, I think this is the quickest way to get a working (as far as I can tell,
and I
didn't play with it all that much, although I did load up the cxxtest.exe,
set a breakpoint,
run through, etc.) DDD 3.3.8 on
12 matches
Mail list logo
