What the..Eterm Installation
 

okay i am trying to install eterm from source and i am getting errors on configure....it's getting stuck at libast_malloc

checking for libast_malloc in -last... no
ERROR: You need LibAST 0.5 or higher to build Eterm. If you already have it, you may have it installed in a strange place, or you may need to run /sbin/ldconfig. If you don't have it, I can download it for you. Shall I retrieve and build LibAST now (y/n)?

Okay so i went and downloaded libast 0.5 source and installed it and all the lib is there except libast_malloc..where the hell do i get this???

don't tell me to get the rpm cuz rpm never works for me..too many dependency prob so not even going to try with rpm..

Okay i am sure libast_malloc doesn't come with libast 0.5...can someone check on their linux box and see where libast_malloc is from?

i have a feeling this is somehow involved with me not having enlightment....

If you loved RPM you'll also love source.
Not only will source need the dependecies the RPM does, it may also need the development version of a library.
There is a development version of libast, you may need this for compiling.
Just guessing.
:)
Good Luck

Heh i just changed the damn configure script to bypass the part where it checks for libast_malloc and it installed and is currently working all right..i will report if something crazy happens with the prog..

just waiting for it to crash and burn..wonder what that malloc thing do...hmmmm ;)

I'm having the same problem. I followed the suggestion to cut out the part of the config script that checks for libast_malloc and the configure script now runs fine. However, make fails immediately with the following:

make all-recursive
make[1]: Entering directory `/usr/local/src/Eterm-0.9.2'
Making all in src
make[2]: Entering directory `/usr/local/src/Eterm-0.9.2/src'
/bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include -I/usr/X11R6/include -g -O2 -c actions.c
../libtool: line1: s%^.*/%%: No such file or directory
../libtool: line1: -e: command not found
../libtool: line1: -e: command not found
../libtool: line1: -e: command not found
../libtool: line1: -e: command not found
../libtool: line1: -e: command not found
../libtool: line1: -e: command not found
../libtool: line1: -e: command not found
../libtool: line1: -e: command not found
../libtool: line1: -e: command not found
../libtool: line1: -e: command not found
../libtool: line1: -e: command not found
../libtool: line1: -e: command not found
../libtool: line1: -e: command not found
:compile: cannot determine name of library object from ' '
make[2]: ***[actions.lo] Error 1
make[2]: Leaving directory `/usr/local/src/Eterm-0.9.2/src'
make[1]: ***[all-recursive] Error 1
make[1]: Leaving directory `/usr/local/src/Eterm-0.9.2'
make: ***[all-recursive-am] Error 2


I'm not sure whether this has anything to do with my alterations of the config script (I've been careful only to remove the section on libast_malloc) or whether it's a completely different problem. Any suggestions??

Slak 9.0
Kernel 2.4.20

It seems to me that it can't find libtool.. at the end of the configure script it displays information about the settings the prog will use to make the prog, such as source path and the path the prog will install to etc etc...did you check to make sure those are correct?? did you check to see if you actually have libtool?? you installed Imlib, libast and other progs eterm says it needs??


oh and run your modified configure in a fresh extracted Eterm folder where it's original configure hasn't been run...

hope this helps

libast_malloc is a function in libast.

yeah i kinda figured that...but do u know what it does?? i think maybe the new libast does not make libast_malloc and eterm's configure is still looking for that file...i think their configure script needs to be updated ;)

Heres a howto on how to fix this problem without editing the configure script.
http://www.gnulinuxhelp.org/howtoz/v...?_howtoz_id=21

WOW!

Thanks for the link. That procedure worked like a charm.

You should post this in the Success stories forum so it doesn't get buried too deeply.