Re: When "aclocal" causes an error message, "sed: invalid option -- 'q'"

2010-11-17 Thread Eric Blake
On 11/17/2010 09:59 AM, Bruce Korb wrote: >> Is it worth installing a temporary sed wrapper earlier in your PATH that >> outputs debugging information such as the process id of its parent if it >> detects that one of the arguments starts with -q? > > Next time I run into it. I unwound everything

bug#7379: On the fix for CVE-2009-4029 Automake security fix for 'make dist*'

2010-11-17 Thread Behdad Esfahbod
Hi Ralf, Scroll down for my comments. On 11/13/10 03:00, Ralf Wildenhues wrote: > [ Thanks Glenn for rerouting the bug report! ] > > Hi Behdad, > >> From: Behdad Esfahbod >> Subject: On the fix for CVE-2009-4029 Automake security fix for 'make dist*' >> Date: Thu, 11 Nov 2010 16:17:22 -0500 >

Re: When "aclocal" causes an error message, "sed: invalid option -- 'q'"

2010-11-17 Thread Bruce Korb
On 11/17/10 07:35, Eric Blake wrote: > On 11/17/2010 08:11 AM, Bruce Korb wrote: >>> OK. I don't see where it should come from in Autoconf nor Automake. >>> Any case the package at hand contains m4_esyscmd in configure.ac that >> ^ >>> contains a

Re: When "aclocal" causes an error message, "sed: invalid option -- 'q'"

2010-11-17 Thread Eric Blake
On 11/17/2010 08:11 AM, Bruce Korb wrote: >> OK. I don't see where it should come from in Autoconf nor Automake. >> Any case the package at hand contains m4_esyscmd in configure.ac that > ^ >> contains a buggy sed script? If not, please state ex

Re: When "aclocal" causes an error message, "sed: invalid option -- 'q'"

2010-11-17 Thread Bruce Korb
On 11/16/10 23:28, Ralf Wildenhues wrote: > * Bruce Korb wrote on Tue, Nov 16, 2010 at 10:18:50PM CET: >> On 11/16/10 12:45, Ralf Wildenhues wrote: >>> This comes probably from autoreconf, not from aclocal. >> That is rather difficult to discern. Either way, the >> controlling program needs to say