GNU bug report logs - #26043
26.0.50; non-portable sed usage in nt/Makefile.in

Previous Next

Package: emacs;

Reported by: Lee B <lboc.home <at> gmail.com>

Date: Fri, 10 Mar 2017 05:58:02 UTC

Severity: normal

Found in version 25.0.93

Fixed in version 26.0.50

Done: Glenn Morris <rgm <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: 26043 <at> debbugs.gnu.org, lboc.home <at> gmail.com
Subject: bug#26043: 25.0.93; Build Failure on OSX
Date: Fri, 10 Mar 2017 19:04:20 +0200
> Cc: 26043 <at> debbugs.gnu.org, Lee B <lboc.home <at> gmail.com>
> From: Paul Eggert <eggert <at> cs.ucla.edu>
> Date: Fri, 10 Mar 2017 08:36:14 -0800
> 
> Just in case it's not clear already, the message "sed: -: No such file 
> or directory" comes from a portability bug in master's nt/Makefile.in. 
> Its line 'sed -f- ${srcdir}/../lib/gnulib.mk > $@-t && \' is not 
> portable, as POSIX says that -f's operand must be a file name, not '-'. 
> Presumably macOS 'sed' does not support the GNU extension where 'sed 
> -f-' reads stdin.

Yes, I know.  This started happening since generation of nt/gnulib.mk
was made mandatory on all platforms; before that this rule was only
used by a Windows build, which uses GNU Sed.




This bug report was last modified 8 years and 69 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.