-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Ralf Wildenhues on 12/1/2006 6:57 AM: >> Avoiding the troublesome line ending seems best to me. > > How does this mesh with > <http://lists.gnu.org/archive/html/autoconf-patches/2001-09/msg00043.html> > or formulated differently, if we're going to break POSIX compatibility, > do we at least have sufficient evidence that all known systems cope with > it?
POSIX requires cat to handle all files, not just text. And I can't find anywhere in POSIX that requires output handed to command substitution to be a text file; command substitution is worded as removing any sequence of one or more newlines, but nothing seems to say that a trailing newline must have been present. And autoconf only uses the file created by AC_LANG_INT_SAVE in `cat conftest.val`. > > FWIW, the patch in that thread undid a previous change that removed the > line ending. Yes, I think that reverting the older patch and removing the \n is safe according to POSIX rules. - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFcDqn84KuGfSFAYARAlOlAJ99iBBlSPX6ZvlBhhWMFOEp8CI62wCfcogO R+2vY6Met+TC+GPjiYT5XIk= =ODDq -----END PGP SIGNATURE-----
