On Tue, 2006-01-10 at 13:55 -0600, Matt Hull wrote: > > On Tue, 10 Jan 2006, Ralf Corsepius wrote: > > > On Tue, 2006-01-10 at 12:16 -0600, Matt Hull wrote: > > > > On Mon, 2006-01-09 at 15:30 -0600, Matt Hull wrote: > > > > > > > > > makefile.am : > > > > > ------------- > > > > > bin_PROGRAMS = mine > > > > > mine_SOURCES = src/main.c > > > > > > > > > > if WITH_GTK1 > > > > > mine_sources += src/gtk2/gtk1.c src/gtk2/gtk1.h > > > > > endif > > > > > > > > > > DIST_SUBDIRS = src src/gtk1 src/gtk2 > > > > > > > > > [EMAIL PROTECTED] ~/mine-0.0.9 $ aclocal -I aclocal.include/ && > > > > > autoheader && autoconf && automake && ./configure && make > > > > > automake: makefile.am: not supported: source file `src/main.c' is in > > > > > subdirectory > > > > > > > > > not sure what is wrong > > > > Which version of automake are you using? The error indicates you might > > > > be using an outdated version (current is 1.9.6). > > > > > i am also testing on an older system that cannot be upgraded, how would i > > > write a toplevel make file for that ? > > > > This feature is only supported in newer automakes (IIRC, since 1.9). It > > doesn't work with older versions of automake.
> my old test system is: > > autoconf version 2.13 > automake version 1.4 > > not my primary computer, just a test one. can not be upgraded. Are you seriously trying to tell us you are developing on such an ancient and outdated system? In this case you are wasting your time of SW which has been abandoned many years ago. You should realize that you don't need autoconf/automake on targets you configure a package on. You need autoconf/automake on those machines you develop the package on. Ralf