Bug#796180: libtool: generates binary data in config.log due to buggy escaping

2018-10-02 Thread Vincent Lefevre
Control: clone -1 -2 Control: reassign -2 libtool Control: retitle -2 libtool: avoid the use of the dangerous, undocumented AC_TRY_EVAL macro, which generates binary data in config.log with dash Control: forwarded -2 https://debbugs.gnu.org/cgi/bugreport.cgi?bug=21309 I've seen in the autoconf

Bug#796180: libtool: generates binary data in config.log due to buggy escaping

2018-10-02 Thread Vincent Lefevre
Control: reassign -1 autoconf 2.69-11 Control: retitle -1 autoconf: missing backslash escaping in AC_TRY_EVAL yields binary data in config.log with dash Control: forwarded -1 http://lists.gnu.org/archive/html/bug-autoconf/2018-10/msg0.html This seems actually to be a bug in autoconf. My new

Bug#796180: libtool: generates binary data in config.log due to buggy escaping

2016-02-08 Thread Vincent Lefevre
Control: found -1 2.4.6-0.1 Control: retitle -1 libtool: generates binary data in config.log with dash due to buggy escaping The problem occurs only with dash, e.g. when setting CONFIG_SHELL=/bin/sh in the environment and where /bin/sh is dash. The problem comes from: + echo configure:10030:

Bug#796180: libtool: generates binary data in config.log due to buggy escaping

2015-08-19 Thread Vincent Lefevre
Package: libtool Version: 2.4.2-1.11 Severity: normal When I run ./configure with MPFR, the generated config.log file contains binary data: configure:9458: /usr/bin/nm -B conftest.o \| sed -n -e 's/^.*[ ]\([ABCDGIRSTW][ABCDGIRSTW]*\)[ ][ ]*\([_A-Za-z][_A-Za-z0-9]*\)$/^A ^B ^B/p' | sed '/

Bug#796180: libtool: generates binary data in config.log due to buggy escaping

2015-08-19 Thread Vincent Lefevre
Control: tags -1 upstream I can reproduce this problem with upstream's libtool 2.4.6 and I've sent a bug report to bug-libtool. -- Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/ Work: CR INRIA - computer