Re: [E-devel] Eterm compilation problem

[<arn...@ti...>]

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... =3D=
)

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 comment the crippled configure file
>> (which first get an error similar to Ryan, this is fixed by
>> commenting out the line
>> 
>> dps_snprintf_oflow()
>
>The correct fix, as has been mentioned previously, is to properly
>build and install LibAST 0.5 (or CVS) before attempting to build Eterm
>0.9.2 (or CVS).  The dps_snprintf_oflow() macro is properly defined in
>libast.m4, which comes with LibAST.
>
>> ./.libs/libEterm.so: undefined reference to `spifopt_usage'
>> ./.libs/libEterm.so: undefined reference to `spifopt_parse'
>> ./.libs/libEterm.so: undefined reference to `spifopt_settings'
>> collect2: ld returned 1 exit status
>> 
>> My C skills are nearly non-existant yet, but I tried to grep the
>> Eterm source for spifopt_usage, spifopt_parse and spifopt_settins
>> and I found no references of them, so I'm guessing there's something
>> missing...
>
>mej@cyborg ~/cvs/eterm/Eterm >> grep spifopt_usage src/*.c
>src/options.c:    spifopt_usage();
>mej@cyborg ~/cvs/eterm/Eterm >> grep spifopt_parse src/*.c
>src/startup.c:    spifopt_parse(argc, argv);
>src/startup.c:    spifopt_parse(argc, argv);
>
>Apparently your grepping skills are right there with your C
>skills. ;-)
>
>Michael
>