Bug 10449 - sed fails to accurately stream file contents
sed fails to accurately stream file contents
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: sed (Show other bugs)
6.1
sparc Linux
medium Severity high
: ---
: ---
Assigned To: Jakub Jelinek
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-03-30 12:54 EST by Dave Torrey
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-03-30 13:09:40 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Dave Torrey 2000-03-30 12:54:41 EST
sed, as packaged with RH6.1-sparc, as well as a fresh compile of sed-3.02,
fails to function accurately on my SparcClassic.  It would reliably drop
the first character of a file, and append a NULL value to the file on
occasion.  This effectively cripples a system by not allowing configure
or other sed-intensive programs to function properly.

I did manage to make it work by explicitly commenting out a #define in
the sed-3.02 Makefiles:

CPPFLAGS= -D_FILE_OFFSET_BITS=64

On a hunch (since the Classic isn't 64-bit), I commented everything after
the = sign, and it appears to work fine.  It had been causing annoying
problems with autoconf scripts, but doesn't when compiled with this
comment.

I'm not sure what the setting really does, but it might be worth looking
into for future RH-sparc releases.  I'm also not sure if it would be a
problem with sed, autoconf, or the system include files, but it manifests
itself in sed, so here 'tis.
Comment 1 Bill Nottingham 2000-03-30 13:09:59 EST
This is fixed in 6.2; it's a glibc problem, IIRC.

Note You need to log in before you can comment on or make changes to this bug.