bugGNU CSSC - Bugs: bug #56507, configure shoudl locate GNU sed in...

 
 

bug #56507: configure shoudl locate GNU sed in order to support Solaris 10

Submitter:  James Youngman <jay>
Submitted:  Mon 17 Jun 2019 10:47:00 AM UTC
   
 
Category:  None Severity:  2 - Minor
Item Group:  None Status:  None
Privacy:  Public Assigned to:  jay
Open/Closed:  Open
* Mandatory Fields

Add a New Comment Rich Markup
   

Mon 17 Jun 2019 10:47:00 AM UTC, original submission:  

On Solaris 10, sed emits an error message if stdin is non-empty but does not end in a newline:

solaris10:~/source/cssc.solaris/releases/1.4.1/CSSC-1.4.1/tests/sact$  env PATH=/usr/ccs/bin:/usr/xpg4/bin:/opt/csw/bin:/usr/bin:/bin  bash -c 'printf "xxx" | sed -e "s/^/# stdout: /"'
sed: Missing newline at end of file standard input.
# stdout: xxx
solaris10:~/source/cssc.solaris/releases/1.4.1/CSSC-1.4.1/tests/sact$  env PATH=/usr/ccs/bin:/usr/xpg4/bin:/opt/csw/bin:/usr/bin:/bin  bash -c 'printf "xxx" | gsed -e "s/^/# stdout: /"'


In the above example, sed was /usr/xpg4/bin/sed.

We should either ensure that sed's input always ends with newline, or find and use GNU sed.

James Youngman <jay>
Group administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by jay (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    No changes have been made to this item

    Back to the top

    Powered by Savane 3.13-f8d8.
    Corresponding source code