[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug-cssc] [bug #56507] configure shoudl locate GNU sed in order to supp
From: |
James Youngman |
Subject: |
[Bug-cssc] [bug #56507] configure shoudl locate GNU sed in order to support Solaris 10 |
Date: |
Mon, 17 Jun 2019 06:47:02 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.108 Safari/537.36 |
URL:
<https://savannah.gnu.org/bugs/?56507>
Summary: configure shoudl locate GNU sed in order to support
Solaris 10
Project: GNU CSSC
Submitted by: jay
Submitted on: 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
Discussion Lock: Any
_______________________________________________________
Details:
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.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?56507>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Bug-cssc] [bug #56507] configure shoudl locate GNU sed in order to support Solaris 10,
James Youngman <=