On 4/22/15 21:53 , Ben McGinnes wrote: > On 22/04/2015 5:22 pm, Werner Koch wrote: >> > On Sat, 18 Apr 2015 21:35, b...@adversary.org said: >> > >>> >> e...@quot.po:54: 'msgid' and 'msgstr' entries do not both end with '\n' >>> >> e...@quot.po:58: 'msgid' and 'msgstr' entries do not both end with '\n' >> > >>> >> but no need to paste them all in); obviously the cause is somewhere >>> >> in those sed or make rules. I'm just not certain of the right place >> > >> > That script (po/quot.po) did not changed for more than a decade. I >> > guess your sed is broken (did you recently update it)? > Nope, there's only one sed on the system, the default one in /usr/bin > and that appears to be the semi-standard FreeBSD one compiled for OS X > Mach. Yes, sed in OS X is a little bit different. “Sed'ing” an output is fine, but when to change/write something in a file it's different.Example:
gnu sed: sed -i 's/foo/bar/g' foobar.txt osx sed: sed -i '' 's/foo/bar/g' foobar.txt I've updated sed to gnu's sed(-4.2 <https://ftp.gnu.org/gnu/sed/>) and it works fine. (+ an updated libiconv). ./configure --prefix=/usr/local --with-libiconv-prefix=/usr/local (Haven't compiled gnupg though). HTH /Eric
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
