Compiling Eterm - frustrating error

[Redwolf]

Okay, I'm having problems compiling Eterm:

the specs:

Slack 9.0
latest sources off www.eterm.org

Okay, so here's the problem:

libscream.c:1402:2: warning: #warning compiling in libscream
 gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include -I/usr/X11R6/include -g -O2 -MT libscream.lo -MD -MP -MF .deps/libscream.Tpo -c libscream.c -o libscream.o >/dev/null 2>&1
/bin/sh ../libtool --mode=compile    -c -o mmx_cmod.lo `test -f 'mmx_cmod.S' || echo './'`mmx_cmod.S
libtool: unrecognized option `-c'
Try `libtool --help' for more information.
make[1]: *** [mmx_cmod.lo] Error 1
make[1]: Leaving directory `/root/Eterm-0.9.2/src'
make: *** [all-recursive] Error 1
root@wolf:~/Eterm-0.9.2#

I can do a './configure' just fine, and I tried using ldconfig before doing anything. I've cleaned and distcleaned. So...why is it not working? Well...obviously, it's trying to pull a command on libtool that DOESN'T EXIST!!! Ahhh...sometyimes you just feel like hurling your computer against the wall...

So how the heck do I fix this?

Oh, yeah:

root@wolf:~/Eterm-0.9.2# libtool --version
ltmain.sh (GNU libtool) 1.5 (1.1220 2003/04/05 19:32:58)

Copyright (C) 2003  Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
root@wolf:~/Eterm-0.9.2#

[nukes]

As far as I can see, -c isn't a valid option, it doesn't appear on the website or in the --help thing. I don't have a manpage for libtool on this box, but you're using the latest version.
I'm downloading the eterm sources to see if I can duplicate this problem on my box, but knowing my luck, it will all go fine.

[nukes]

AS i thought, it worked flawlessly. Hmm. Slack 9 uses GCC 3.2 doesn't it?
It worked for me using CFLAGS="-mcpu=athlon-xp -O4 -pipe"
I did find a slack package for an older version here:
http://www.linuxpackages.net/redirec.../Eterm-0.8.10/
Its for slack7 though. Also, you could probably use rpm2tgz and install the RPM from the eterm.org site.

Upon examining the makefile, I found this:

LTCOMPILE = $(LIBTOOL) --mode=compile $(CC) $(DEFS) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS)

Which means that between the --mode=compile and -c you should have the name of your C compiler (gcc) check that the CC environment variable is set (echo $CC in a command line) if it isn't set, export it.
Just in case you are interested means that GCC should compile and assemble the code, but not link it into an executable.
If all else fails, try building that specific target by hand, then the make may continue.
I hope at least some of that helps you.

[Redwolf]

I've got my computer off right now due to a certain heating problem...using a different machine. I'll try your flags, then try exporting $CC if that doesn't work next time I get to the machine. Worse comes to worse, I use Alien (package coverter) as you suggest.

[Redwolf]

Okay, I tried giving it your same flags, but it balked at that...said it didn't recognize -04, -mcpu, or -pipe when I trried them, individually afterwards. Did you mean ldconfig or configure?

I also tried exporting cc, to no avail. Did:
export CC=/usr/bin/cc
gave the exact same error. Hmmm...