aterm compilation problems

taltman · 07-13-2004, 12:16 AM

I recently d/l aterm 0.4.2
I unpacked it and read the INSTALL file.
I followed the directions and ran

Code:

$ ./configure
loading cache ./config.cache
configuring for aterm 0.4.2
checking for gcc... (cached) gcc
checking whether the C compiler (gcc -march=athlon-xp -O2 -msse -finline-functions 
-falign-jumps=5 -falign-loops=5 -pipe -fomit-frame-pointer ) works... yes
checking whether the C compiler (gcc -march=athlon-xp -O2 -msse -finline-functions 
-falign-jumps=5 -falign-loops=5 -pipe -fomit-frame-pointer ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking how to run the C preprocessor... (cached) gcc -E
checking for a BSD compatible install... (cached) /usr/bin/ginstall -c
checking for mv... (cached) /usr/bin/mv
checking for rm... (cached) /usr/bin/rm
checking for cp... (cached) /usr/bin/cp
checking for sed... (cached) /usr/bin/sed
checking for AIX... no
checking for POSIXized ISC... no
checking for X... (cached) libraries /usr/X11R6/lib, headers /usr/X11R6/include
checking for dnet_ntoa in -ldnet... (cached) no
checking for dnet_ntoa in -ldnet_stub... (cached) no
checking for gethostbyname... (cached) yes
checking for connect... (cached) yes
checking for remove... (cached) yes
checking for shmat... (cached) yes
checking for IceConnectionNumber in -lICE... (cached) yes
checking for libXpm... (cached) -I, -L/usr/X11/lib
checking for libjpeg... (cached) -I, -L
checking for libpng... (cached) -I, -L
checking for AfterStep libraries... (cached) no
checking for sys/wait.h that is POSIX.1 compatible... (cached) yes
checking for assert.h... (cached) yes
checking for fcntl.h... (cached) yes
checking for grp.h... (cached) yes
checking for libc.h... (cached) no
checking for lastlog.h... (cached) yes
checking for stdarg.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for termios.h... (cached) yes
checking for unistd.h... (cached) yes
checking for utmpx.h... (cached) yes
checking for sys/byteorder.h... (cached) no
checking for sys/ioctl.h... (cached) yes
checking for sys/select.h... (cached) yes
checking for sys/sockio.h... (cached) no
checking for sys/time.h... (cached) yes
checking whether time.h and sys/time.h may both be included... (cached) yes
checking for getpt... (cached) yes
checking for working const... (cached) yes
checking for inline... (cached) inline
checking for ANSI C header files... (cached) yes
checking for mode_t... (cached) yes
checking for pid_t... (cached) yes
checking for uid_t in sys/types.h... (cached) yes
checking size of char... (cached) 1
checking size of short... (cached) 2
checking size of int... (cached) 4
checking size of long... (cached) 4
checking size of int *... (cached) 4
checking return type of signal handlers... (cached) void
checking for atexit... (cached) yes
checking for unsetenv... (cached) yes
checking for setutent... (cached) yes
checking for seteuid... (cached) yes
checking for host in utmp struct... (cached) yes
checking where utmp is located... (cached) /var/run/utmp
checking where wtmp is located... (cached) /var/log/wtmp
checking where ttys/ttytab is located... 
checking for working Xlocale... (cached) yes
checking for working setlocale... (cached) no
creating ./config.status
creating autoconf/Make.common
sed: file conftest.s1 line 4: Unterminated `s' command
creating Makefile
sed: file conftest.s1 line 4: Unterminated `s' command
creating doc/Makefile
sed: file conftest.s1 line 4: Unterminated `s' command
creating src/Makefile
sed: file conftest.s1 line 4: Unterminated `s' command
creating src/graphics/Makefile
sed: file conftest.s1 line 4: Unterminated `s' command
creating scripts/random_colors
sed: file conftest.s1 line 4: Unterminated `s' command
creating config.h
config.h is unchanged
Configuration:

  Aterm version:              0.4.2 : 06 September 01
  Source code location:       .
  Install path:               /usr/local/bin
  Compiler:                   gcc
  Compiler flags:             -march=athlon-xp -O2 -msse -finline-functions 
-falign-jumps=5 -falign-loops=5 -pipe -fomit-frame-pointer
    without any AfterStep integration.

  Transparency :		enabled
  Off focus fading :		disabled

  malloc support:             system default

The following are set in config.h

  utmp support:               disabled

  Type of 16bit:               short
          32bit:               int
          pointer:             (same as) int

  *** Please check src/feature.h for further options ***

$ make
make: *** No targets.  Stop.

I then viewed the make file and it was empty.

The same thing happened when I tried to compile aterm 0.4.1
This is the only thing I have compiled on my fresh slack 10 system
besides the 2.6.7 kernel...it took a few tries on the kernel but I
thought that was because I have a newer version of gcc than recommended.

The md5 of the aterm package is
d046fcf7fadd661dd5efb393a43c57b1

I couldn't find it on their site to verify.

I am not sure if it is a problem with gcc or just with aterm.
I have installed slack 10 a few times and the media has been verified with md5.

veritas · 07-13-2004, 02:15 AM

I got the same md5 as you, of the aterm-0.4.2.tar.gz file. And I was able to ./configure, make and make install just fine. So its definately not a problem with the file. Could be a problem with your installation? Btw, the location of the file I download is:

http://heanet.dl.sourceforge.net/sou...m-0.4.2.tar.gz

taltman · 07-13-2004, 12:40 PM

I installed slack 10 from the cds.
I verified the iso before I burned.
I have also reinstalled a few times.
The only extra thing I have is 2.6.7
Also that link doesn't work for me.

I'll try to compile it with the 2.4.26 kernel, to reinstall gcc, and
to reinstall slack.

I will post the results.

keefaz · 07-13-2004, 01:17 PM

Did you install the automake package ?

taltman · 07-13-2004, 05:15 PM

ok I tried it with the base kernel and it didn't work.
I began to reinstall slack and after awhile received a fatal kernel
error about it not being to access memory location such and such.
I started the insallation again(not really sure what to do) and I used
the bareacpi.i kernel instead of bare.i, the installation went through perfectly.
I logged in added my user and went off to /home(which was a separate partition)
i went into the aterm directory and ran make and it worked.
I didn't install it because i wanted to go add my 2.6.7 kernel first.
I went to install the kernel and received an internal compiler error after a few
minutes of make.
I tried compiling a few more times and I received a different error each time.

oh and automake was installed on the original system.

Shade · 07-13-2004, 05:31 PM

This is beginning to sound like a hardware problem.

Random compiler errors are a good sign that something in your system is starting to fail -- I'm betting on the disk, IDE bus, or memory.
I'd try running memtest86 (search google for this little app) first to test your memory. Let it run overnight.

This is the main thing that bothers me:

Quote:

I began to reinstall slack and after awhile received a fatal kernel
error about it not being to access memory location such and such.

That's a pretty good sign of failing memory.

--Shade

taltman · 07-13-2004, 05:37 PM

I just built my computer,so maybe I recieved a bad part.
I have 1GB of memory and I just assumed the error was because
the bare.i kernel doesn't support 1GB or memory.
I will grab the app and run it.
Thank you all for your help and time.

Shade · 07-13-2004, 05:54 PM

New components are most vulnerable to failure -- I assure you, the kernel supports 1gig of memory

--Shade

taltman · 07-13-2004, 07:05 PM

Well like I said i just assumed because I read somewhere about you having to
enable something when you compile the kernel to support 1GB.
When I booted my 2.6.7 it gave me a warning saying I needed to enable the option also.

I was having some trouble with the hardware before so it doesn't surprise me
that it is at fault.

There is some bad memory according to the memtest86 program.
It's a pretty cool app thanks for pointing it out.

I'm sorry if what I said came across as me not believing you because that is surely not what I intended.

I guess all I can do now is let memtest finish running and pray only one dimm is
bad.

Once again thank you all for your help.
I appreciate it very much.

taltman · 07-13-2004, 07:54 PM

I bought my ram and mobo from newegg.com and I just went there to
check the warranty.
Someone has posted a comment about how the ram doesn't work with his mobo.
The comment was not there when I purchased it.
He has the same specs as I.

I have an ASUS A7N8X-E Deluxe and Kingston 184 Pin 512MB DDR PC-3200 Model# KVR400X64C3A/512

Now even though this ram is on the Asus supported list for the mobo
it apparently still has problems if the memory modules are not from the correct
manufacturer.

keefaz · 07-14-2004, 04:58 AM

Also did you install your 2.6.7 kernel as package ? If yes, did you install the corresponding kernel-source package too ?

taltman · 07-14-2004, 03:07 PM

No, I compiled from source.
The problem was with the ram.