[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

grep 2.3-7 is broken (was Re: compiler issues and some booboos)



It seems there is a problem using grep 2.3-7.  I got the same problem when I
upgraded libc6 from slink to potato on my SparcClassic but has gone away after
upgraded grep to 2.3-5.  I got a reply from Sharkey who told me that 2.3-5 is
working well even on ultrasparc (2.3-5 is still available from
ftp://lix.polytechnique.fr/pub/Linux/debian/sparc/exp if you need to downgrade
to).

Is there somebody who would want to check why it breaks ?
I don't have time myself to work on.
Sorry.


sharkey@ale.physics.sunysb.edu wrote:
> > > 2. grep is failing with messages like:
> > > 
> > > grep: guile-core_1.3.4-0.diff.gz: Bad address
> > > grep: guile-core_1.3.4-0.dsc: Bad address
> > > grep: guile-core_1.3.4-0_sparc.changes: Bad address
> > > grep: guile-core_1.3.4.orig.tar.gz: Bad address
> > > grep: guile1.3_1.3.4-0_sparc.deb: Bad address
> > > grep: libguile6-dev_1.3.4-0_sparc.deb: Bad address
> > > grep: libguile6-slib_1.3.4-0_sparc.deb: Bad address
> > > grep: libguile6_1.3.4-0_sparc.deb: Bad address
> > > 
> > > making grep useless.  I tried recompiling from source but it made no
> > > difference at all.
> > 
> > Until I installed grep 2.3-5 from potato I got the same errors.
> 
> I've got those errors too:
> 
> nupc36% grep -i dma *.c 
> grep: amd7930.c: Bad address
> grep: audio.c: Bad address
> grep: cs4231.c: Bad address
> grep: dbri.c: Bad address
> grep: dmy.c: Bad address
> 
> And I'm up to date, with potato:
> 
> nupc36% dpkg --status grep | grep -i version
> Version: 2.3-7
> 
> (As you can see, grep seems to work fine when reading from stdin.)
> 
> > However it was fixed in this version, maybe only on old sparc ? In fact, I'm
> > running Debian on a SparcClassic.
> 
> I'm running on an Ultra 1.

-- 
 Eric Delaunay                 | "La guerre justifie l'existence des militaires.
 delaunay@lix.polytechnique.fr | En les supprimant." Henri Jeanson (1900-1970)


Reply to: