Because:
1. Firefox depends on autoconf 2.13 to generate all configure files, the
one shipped with CBE is 2.60
2. After the patch has been upstreamed ( I'm pushing it to the
community), there is no need to run autoconf anymore
because configure file will be updated in the community code base.
Laszlo (Laca) Peter wrote:
> On Thu, 2007-03-22 at 12:36 +0800, brian.lu wrote:
>
>
>> I've discussed this with Dave. He thinks that it's more convenient to
>> patch configure. I've posted a patch in the community which patches
>> configure.in.
>>
>
> How so? Why is it more convenient to have a longish patch of a
> generated file than adding a single line to the source (configure.in)
> and running autoconf?
>
> Laca
>
>
>
>
>
