Re: bug in autoconf-2.64

2011-02-23 Thread Ralf Wildenhues
[ this is http://thread.gmane.org/gmane.comp.sysutils.autoconf.bugs/7834 from http://gcc.gnu.org/ml/gcc-patches/2011-02/msg01480.html adding bug-gnulib; followups can elide bug-autoconf ] * Ralf Wildenhues wrote on Thu, Feb 24, 2011 at 07:24:35AM CET: > IOW, it looks like the replacement code

Re: bug in autoconf-2.64

2011-02-23 Thread Ralf Wildenhues
* Mike Stump wrote on Thu, Feb 24, 2011 at 12:06:07AM CET: > On Feb 23, 2011, at 1:37 PM, Eric Blake wrote: > > Are you on a machine with SSE4.2 instructions? > > Core 2 Duo. darwin10 (aka SnowLeopard). No glibc. Here no SSE4.2 either. In an up to date build tree of the commit that exposes the

Re: bug in autoconf-2.64

2011-02-23 Thread Mike Stump
On Feb 23, 2011, at 1:37 PM, Eric Blake wrote: > Are you on a machine with SSE4.2 instructions? Core 2 Duo. darwin10 (aka SnowLeopard). No glibc.

Re: bug in autoconf-2.64

2011-02-23 Thread Eric Blake
On 02/23/2011 02:33 PM, Ralf Wildenhues wrote: > * Ralf Wildenhues wrote on Wed, Feb 23, 2011 at 09:08:07PM CET: >> I can confirm the issue, but my bisect ended at >> 5e763da323f3927159b6c151f186569a9929ddbe instead. > >> I'm starting bisect over the gnulib update in above commit now, >> which ran

Re: bug in autoconf-2.64

2011-02-23 Thread Ralf Wildenhues
* Ralf Wildenhues wrote on Wed, Feb 23, 2011 at 09:08:07PM CET: > I can confirm the issue, but my bisect ended at > 5e763da323f3927159b6c151f186569a9929ddbe instead. > I'm starting bisect over the gnulib update in above commit now, > which ranges from c0ebdfe226c38c72db7c1944113fd19ff534e362 to >

Re: bug in autoconf-2.64

2011-02-23 Thread Ralf Wildenhues
Hello, * Peter O'Gorman wrote on Wed, Feb 23, 2011 at 04:50:32AM CET: > Unless I did it wrong (entirely possible) - > 76d1c49b8056aaf3f1046ba19c6dea6eb6aecb78 is the first bad commit - I can confirm the issue, but my bisect ended at 5e763da323f3927159b6c151f186569a9929ddbe instead. (You need to u