Branden Robinson writes:
> On Wed, Mar 03, 2004 at 11:02:15AM +0100, Matthias Klose wrote:
> > Branden Robinson writes:
> > > Package: gcc-3.3
> > > Version: 1:3.3.3-0pre3
> > > Severity: normal
> > > 
> > > [I checked 1:3.3.3-1, and it doesn't have this functionality, either.]
> > > 
> > > Please apply the following patches from upstream CVS so that glibc can
> > > also be modified to support backtracing on ia64.
> > > 
> > > http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-3_3-branch&r1=1.16114.2.784&r2=1.16114.2.785
> > > http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/config/ia64/unwind-ia64.c.diff?cvsroot=gcc&only_with_tag=gcc-3_3-branch&r1=1.13.2.2&r2=1.13.2.3
> > 
> > these are changes from last October already applied in both package versions
> > you checked. I'm confused ...
> 
> Huh; when I unpacked the package and ran "debian/rules patch", I didn't
> see the changes.

debian/rules unpack

> But then too, the patch rule did produce some scary-looking warnings.
> Is that the right way to inspect the unpacked source tree?

the change is not in the debian patches, but in the upstream gcc-3.3.3
tarball (and was in the gcc-3.3.2 upstream tarball).


Reply via email to