From: "W. Lincoln Harvey" via "Bug reports for GUILE, GNU's Ubiquitous Extension Language" <bug-guile@gnu.org>
To: 39999@debbugs.gnu.org
Subject: bug#39999: MacOS Catalina with sed
Date: Wed, 29 Apr 2020 11:22:00 -0700 [thread overview]
Message-ID: <073D0C3D-DE24-48EE-A0D6-272D14B47655@mac.com> (raw)
In-Reply-To: <12F04DBA-35DF-49B3-B2BB-B07A95550151@gmail.com>
MacOS uses BSD sed. When the -i option to sed is used, it has a mandatory argument, which should be a zero length string to edit the file in-place.
Gnu sed’s -i option uses an optional argument, rather than a mandatory argument, which if not present allows the file to be edited in-place. Adding a zero-length string might cause problems.
Configure needs to add a zero length quote when compiling using BSD sed, and nothing when compiling using Gnu sed, or avoid the whole problem by making a backup using a prefix, in which case both use the same syntax.
wlh
next prev parent reply other threads:[~2020-04-29 18:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 13:29 bug#39999: make install fails on mac (Catilina, Guile-3.0.1) Massimiliano Gubinelli
2020-03-11 11:11 ` Ludovic Courtès
2020-03-11 11:20 ` Massimiliano Gubinelli
2020-03-11 14:04 ` Ludovic Courtès
2020-04-29 18:22 ` W. Lincoln Harvey via Bug reports for GUILE, GNU's Ubiquitous Extension Language [this message]
2020-04-29 19:30 ` bug#39999: BSD sed vs Gnu sed W. Lincoln Harvey via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2020-04-30 0:04 ` Greg Troxel
2020-04-30 0:37 ` bug#39999: sed -i non-POSIX wlharvey4--- via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2020-05-01 14:37 ` Greg Troxel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=073D0C3D-DE24-48EE-A0D6-272D14B47655@mac.com \
--to=bug-guile@gnu.org \
--cc=39999@debbugs.gnu.org \
--cc=lincolnlaw@mac.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).