On Monday, 31 March 2003, at 01:42:22 (+),
[EMAIL PROTECTED] wrote:
> the reason Eterm didn't compile was because of an old version of
> libAST, anyway, it compiled fine now so I think I'll go stand in the
> corner... =)
A spanking! A spanking!
;-)
Michael
--
Michael Jennings (a.k.a. Kai
the reason Eterm didn't compile was because of an old version of libAST,
anyway, it compiled fine now so I think I'll go stand in the corner... =)
thanks for the reply
/Thomas
>> I also had some autoconf (I have version 2.13, which version is
>> needed?)
>
>2.13
>
>> errors, however I managed to
On Friday, 28 March 2003, at 08:33:00 (+),
[EMAIL PROTECTED] wrote:
> I also had some autoconf (I have version 2.13, which version is
> needed?)
2.13
> errors, however I managed to comment the crippled configure file
> (which first get an error similar to Ryan, this is fixed by
> commenting
I also had some autoconf (I have version 2.13, which version is needed?)
errors, however I managed to comment the crippled configure file
(which first get an error similar to Ryan, this is fixed by commenting out
the line
dps_snprintf_oflow()
it then tries to download and compile libAST 0.5, conf
On Thursday, 27 March 2003, at 13:19:03 (-0800),
Ryan wrote:
> I haven't been able to compile Eterm for 3 weeks. Here is the error that
> configure is spitting at me:
>
> ./configure: line 11150: syntax error near unexpected token `echo'
> ./configure: line 11150: `echo "$as_me:$LINENO: checking
I haven't been able to compile Eterm for 3 weeks. Here is the error that
configure is spitting at me:
./configure: line 11150: syntax error near unexpected token `echo'
./configure: line 11150: `echo "$as_me:$LINENO: checking for pow in -lm" >&5'
Sorry to post this to the list, I dont know how t
