On Friday 11 January 2013 12:21:24 Stefano Lattarini wrote:
> On 01/11/2013 06:11 PM, Mike Frysinger wrote:
> > On Friday 11 January 2013 04:08:26 Stefano Lattarini wrote:
> >> On 01/11/2013 05:07 AM, Mike Frysinger wrote:
> >>> i can't imagine this is a big runtime penalty, so why does configure
>
On 01/11/2013 06:11 PM, Mike Frysinger wrote:
> On Friday 11 January 2013 04:08:26 Stefano Lattarini wrote:
>> On 01/11/2013 05:07 AM, Mike Frysinger wrote:
>>> i can't imagine this is a big runtime penalty, so why does configure
>>> check for the perl's thread settings and then hardcode that in th
On Friday 11 January 2013 04:08:26 Stefano Lattarini wrote:
> On 01/11/2013 05:07 AM, Mike Frysinger wrote:
> > i can't imagine this is a big runtime penalty, so why does configure
> > check for the perl's thread settings and then hardcode that in the
> > generated automake ?
>
> I don't know, I w
[+cc automake-patches, since patches should be discussed there]
On 01/11/2013 05:07 AM, Mike Frysinger wrote:
> i can't imagine this is a big runtime penalty, so why does configure check
> for
> the perl's thread settings and then hardcode that in the generated automake ?
>
I don't know, I wasn'
i can't imagine this is a big runtime penalty, so why does configure check for
the perl's thread settings and then hardcode that in the generated automake ?
it means if you change your perl config or deploy an automake package on a
system that has threads disabled, you get errors when trying to
