The dot character in the configure script was not the only error, just
the only one discussed in the autoconf thread. The other errors look
similar may be due to same problem.
Here are the details. Read through this to the end and I think it
looks pretty obvious.
Here is the total output of
On Thu, 3 Jun 2010, Vincent Torri wrote:
>
>
> On Thu, 3 Jun 2010, Gustavo Sverzut Barbieri wrote:
>
>> On Thu, Jun 3, 2010 at 3:10 PM, Dave Ray wrote:
>>> I attempted to compile e17 on MacOS-X Leopard (10.5.8) after doing a
>>> fresh OS install.
>>>
>>> All autoconf.sh scripts are failing in a
On Jun 3, 2010, at 12:17 PM, Gustavo Sverzut Barbieri wrote:
> On Thu, Jun 3, 2010 at 3:10 PM, Dave Ray wrote:
>> ...
>> According to the thread, configure.ac contains a non-portable use of
>> sed that is causing the failure only on MacOS.
>> ...
>
> Possibly it was Sachiel's changes from yesterd
On Thu, 3 Jun 2010, Gustavo Sverzut Barbieri wrote:
> On Thu, Jun 3, 2010 at 3:10 PM, Dave Ray wrote:
>> I attempted to compile e17 on MacOS-X Leopard (10.5.8) after doing a
>> fresh OS install.
>>
>> All autoconf.sh scripts are failing in an unusual way.
>>
>> Spoke to Vincent Torri, who poste
On Thu, Jun 3, 2010 at 3:10 PM, Dave Ray wrote:
> I attempted to compile e17 on MacOS-X Leopard (10.5.8) after doing a
> fresh OS install.
>
> All autoconf.sh scripts are failing in an unusual way.
>
> Spoke to Vincent Torri, who posted my problem on the M4 list. You can
> read the whole thread he
I attempted to compile e17 on MacOS-X Leopard (10.5.8) after doing a
fresh OS install.
All autoconf.sh scripts are failing in an unusual way.
Spoke to Vincent Torri, who posted my problem on the M4 list. You can
read the whole thread here:
http://lists.gnu.org/archive/html/autoconf/2010-06/ms
