Hi, that is exactly what I did (if you look the end of my previous mail).
glibtoolize , aclocal and autoheader calls succeeds as far as I understand but automake fails as follows (snipped it, see the comple list at the end of mail): nyholkumac2:trunk nyholku$ glibtoolize --force You should update your `aclocal.m4' by running aclocal. nyholkumac2:trunk nyholku$ aclocal configure.ac:107: warning: macro `AM_PROG_LIBTOOL' not found in library nyholkumac2:trunk nyholku$ autoheader nyholkumac2:trunk nyholku$ automake --force-missing --add-missing cli/Makefile.am:5: Libtool library used but `LIBTOOL' is undefined cli/Makefile.am:5: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' cli/Makefile.am:5: to `configure.ac' and run `aclocal' and `autoconf' again. cli/Makefile.am:5: If `AC_PROG_LIBTOOL' is in `configure.ac', make sure cli/Makefile.am:5: its definition is in aclocal's search path. So it seems I'm missing something (AM_PROG_LIBTOOL?) but I don't know what is the proper way to fix it. My previous attempts with other projectes of similar scope and tool chain discrourage me to just wildly hack...it never seems to get me anywhere! br Kusti >>> borut.ra...@siol.net 10.2.2009 13:15:31 >>> Kusta, try the following: $ glibtoolize --force $ aclocal $ autoheader $ automake --force-missing --add-missing $ autoconf $ ./configure $ make Borut Kustaa Nyholm wrote: > >> borut.ra...@siol.net 10.2.2009 12:36:46 >>> >> > > >> >> Can you try to compile the version without gui from svn trunk to see if >> gtk+* is really needed? Probably you have to uninstall gtk+* package >> before that... >> > > I'm trying it as but it is not going well. See results at end of this mail. > > Help would be appreciated as I'm not too familiar with the autotools. > > BTW (referring to the gpsim instructions page) libtoolize seems to be > glibtoolize on Mac OS X, a small detail that is enough to stump a beginner. > > > > > >> What about the question I sent you in previous mail about Mac OS X >> architecture and running regression tests? >> > > > Ran it, sent it, now it seems to be on hold because it was >40k, > > I can sed it directly to you. > > > BTW I just retried to subscribe to gpsim and this time it seems > like it succeeded, last time when I replied to the confirmation > message there was just some error page, can't recall the details anymore. > > > br Kusti > > > *----------------------- > > > nyholkumac2:trunk nyholku$ glibtoolize > You should update your `aclocal.m4' by running aclocal. > glibtoolize: `config.guess' exists: use `--force' to overwrite > glibtoolize: `config.sub' exists: use `--force' to overwrite > glibtoolize: `ltmain.sh' exists: use `--force' to overwrite > nyholkumac2:trunk nyholku$ glibtoolize --force > You should update your `aclocal.m4' by running aclocal. > nyholkumac2:trunk nyholku$ aclocal > configure.ac:107: warning: macro `AM_PROG_LIBTOOL' not found in library > nyholkumac2:trunk nyholku$ autoheader > nyholkumac2:trunk nyholku$ automake --add-missing > cli/Makefile.am:5: Libtool library used but `LIBTOOL' is undefined > cli/Makefile.am:5: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' > cli/Makefile.am:5: to `configure.ac' and run `aclocal' and `autoconf' again. > cli/Makefile.am:5: If `AC_PROG_LIBTOOL' is in `configure.ac', make sure > cli/Makefile.am:5: its definition is in aclocal's search path. > eXdbm/Makefile.am:22: Libtool library used but `LIBTOOL' is undefined > eXdbm/Makefile.am:22: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' > eXdbm/Makefile.am:22: to `configure.ac' and run `aclocal' and `autoconf' again. > eXdbm/Makefile.am:22: If `AC_PROG_LIBTOOL' is in `configure.ac', make sure > eXdbm/Makefile.am:22: its definition is in aclocal's search path. > gui/Makefile.am:5: Libtool library used but `LIBTOOL' is undefined > gui/Makefile.am:5: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' > gui/Makefile.am:5: to `configure.ac' and run `aclocal' and `autoconf' again. > gui/Makefile.am:5: If `AC_PROG_LIBTOOL' is in `configure.ac', make sure > gui/Makefile.am:5: its definition is in aclocal's search path. > modules/Makefile.am:5: Libtool library used but `LIBTOOL' is undefined > modules/Makefile.am:5: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' > modules/Makefile.am:5: to `configure.ac' and run `aclocal' and `autoconf' again. > modules/Makefile.am:5: If `AC_PROG_LIBTOOL' is in `configure.ac', make sure > modules/Makefile.am:5: its definition is in aclocal's search path. > src/Makefile.am:5: Libtool library used but `LIBTOOL' is undefined > src/Makefile.am:5: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' > src/Makefile.am:5: to `configure.ac' and run `aclocal' and `autoconf' again. > src/Makefile.am:5: If `AC_PROG_LIBTOOL' is in `configure.ac', make sure > src/Makefile.am:5: its definition is in aclocal's search path. > src/dspic/Makefile.am:5: Libtool library used but `LIBTOOL' is undefined > src/dspic/Makefile.am:5: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' > src/dspic/Makefile.am:5: to `configure.ac' and run `aclocal' and `autoconf' again. > src/dspic/Makefile.am:5: If `AC_PROG_LIBTOOL' is in `configure.ac', make sure > src/dspic/Makefile.am:5: its definition is in aclocal's search path. > nyholkumac2:trunk nyholku$ autoconf > nyholkumac2:trunk nyholku$ ./configure --disable-gui > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... ./install-sh -c -d > checking for gawk... no > checking for mawk... no > checking for nawk... no > checking for awk... awk > checking whether make sets $(MAKE)... yes > checking whether to enable maintainer-specific portions of Makefiles... no > checking build system type... i686-apple-darwin9.6.0 > checking host system type... i686-apple-darwin9.6.0 > disabling gui support > disabling gpsim socket interface > checking for style of include used by make... GNU > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ISO C89... none needed > checking dependency style of gcc... gcc3 > checking how to run the C preprocessor... gcc -E > checking for grep that handles long lines and -e... /usr/bin/grep > checking for egrep... /usr/bin/grep -E > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking popt.h usability... yes > checking popt.h presence... yes > checking for popt.h... yes > checking for pkg-config... /opt/local/bin/pkg-config > checking readline/readline.h usability... yes > checking readline/readline.h presence... yes > checking for readline/readline.h... yes > checking for GNU Readline library -lreadline.dll... no > checking for GNU Readline library -lreadline... yes > checking for g++... g++ > checking whether we are using the GNU C++ compiler... yes > checking whether g++ accepts -g... yes > checking dependency style of g++... gcc3 > checking how to run the C++ preprocessor... g++ -E > checking for gcc... (cached) gcc > checking whether we are using the GNU C compiler... (cached) yes > checking whether gcc accepts -g... (cached) yes > checking for gcc option to accept ISO C89... (cached) none needed > checking dependency style of gcc... (cached) gcc3 > checking how to run the C preprocessor... gcc -E > checking for a BSD-compatible install... /usr/bin/install -c > checking whether ln -s works... yes > checking whether make sets $(MAKE)... (cached) yes > checking for bison... bison -y > checking for flex... flex > checking lex output file root... lex.yy > checking lex library... -lfl > checking whether yytext is a pointer... yes > ./configure: line 6873: AM_PROG_LIBTOOL: command not found > checking for main in -lpopt... no > checking for ANSI C header files... (cached) yes > checking fcntl.h usability... yes > checking fcntl.h presence... yes > checking for fcntl.h... yes > checking netdb.h usability... yes > checking netdb.h presence... yes > checking for netdb.h... yes > checking netinet/in.h usability... yes > checking netinet/in.h presence... yes > checking for netinet/in.h... yes > checking stddef.h usability... yes > checking stddef.h presence... yes > checking for stddef.h... yes > checking for stdint.h... (cached) yes > checking for stdlib.h... (cached) yes > checking for string.h... (cached) yes > checking sys/file.h usability... yes > checking sys/file.h presence... yes > checking for sys/file.h... yes > checking sys/ioctl.h usability... yes > checking sys/ioctl.h presence... yes > checking for sys/ioctl.h... yes > checking sys/socket.h usability... yes > checking sys/socket.h presence... yes > checking for sys/socket.h... yes > checking sys/time.h usability... yes > checking sys/time.h presence... yes > checking for sys/time.h... yes > checking termios.h usability... yes > checking termios.h presence... yes > checking for termios.h... yes > checking for unistd.h... (cached) yes > checking for stdbool.h that conforms to C99... yes > checking for _Bool... no > checking for an ANSI C-conforming const... yes > checking for inline... inline > checking for size_t... yes > checking whether time.h and sys/time.h may both be included... yes > checking return type of signal handlers... void > checking for working alloca.h... yes > checking for alloca... yes > checking whether gcc needs -traditional... no > checking for stdlib.h... (cached) yes > checking for GNU libc compatible malloc... yes > checking for stdlib.h... (cached) yes > checking for GNU libc compatible realloc... yes > checking sys/select.h usability... yes > checking sys/select.h presence... yes > checking for sys/select.h... yes > checking for sys/socket.h... (cached) yes > checking types of arguments for select... int,fd_set *,struct timeval * > checking for working strtod... yes > checking for floor... yes > checking for gethostbyname... yes > checking for gethostname... yes > checking for gettimeofday... yes > checking for memset... yes > checking for pow... yes > checking for select... yes > checking for socket... yes > checking for sqrt... yes > checking for strcasecmp... yes > checking for strchr... yes > checking for strdup... yes > checking for strerror... yes > checking for strncasecmp... yes > checking for strndup... no > checking for strpbrk... yes > checking for strrchr... yes > checking for strstr... yes > checking for strtoul... yes > checking size of long... 4 > configure: creating ./config.status > config.status: error: cannot find input file: Makefile.in > nyholkumac2:trunk nyholku$ > > > ------------------------------------------------------------------------------ > Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) > software. With Adobe AIR, Ajax developers can use existing skills and code to > build responsive, highly engaging applications that combine the power of local > resources and data with the reach of the web. Download the Adobe AIR SDK and > Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com > _______________________________________________ > Sdcc-user mailing list > Sdcc-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sdcc-user > > ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
