Greetings, I was waiting for something else to finish (another software build), so I got the crazy idea of trying to build AllStarLink on my BeagleBoard. Below shows that I did not get very far in the build before an error ocurred. I bet that if I had a complete install kit, I could make this work. I'll have to take a look at what is actually on the ACID CD to see if I can port stuff over. I'll leave that for a project later in the week. :) 8-Dale root@walter:/usr/src/astsrc# make upgrade-acid (cd zaptel; ./configure) 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 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 for GNU make... make checking for grep... /bin/grep checking for sh... /bin/bash checking for ln... /bin/ln checking for wget... /usr/bin/wget checking for grep that handles long lines and -e... (cached) /bin/grep checking for egrep... /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 for initscr in -lcurses... yes checking curses.h usability... yes checking curses.h presence... yes checking for curses.h... yes checking for initscr in -lncurses... yes checking for curses.h... (cached) yes checking for newtBell in -lnewt... no checking for usb_init in -lusb... no configure: creating ./config.status config.status: creating build_tools/menuselect-deps config.status: creating makeopts config.status: creating build_tools/make_firmware_object configure: *** Zaptel build successfully configured *** (MAKELEVEL=0; make -C zaptel install) make: Entering directory `/usr/src/astsrc/zaptel' make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' checking build system type... armv7l-unknown-linux-gnu checking host system type... armv7l-unknown-linux-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 ANSI C... none needed checking for GNU make... make checking for asprintf... yes checking for getloadavg... yes checking for setenv... yes checking for strcasestr... yes checking for strndup... yes checking for strnlen... yes checking for strsep... yes checking for strtoq... yes checking for unsetenv... yes checking for vasprintf... yes checking how to run the C preprocessor... gcc -E checking for egrep... 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 for initscr in -lcurses... yes checking curses.h usability... yes checking curses.h presence... yes checking for curses.h... yes checking for initscr in -lncurses... yes checking for curses.h... (cached) yes checking for pkg-config... pkg-config Package gtk+-2.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `gtk+-2.0.pc' to the PKG_CONFIG_PATH environment variable No package 'gtk+-2.0' found configure: creating ./config.status config.status: creating makeopts config.status: creating autoconfig.h configure: configuring in mxml configure: running /bin/bash './configure' --prefix=/usr/local 'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=. 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 ANSI C... none needed checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for a BSD-compatible install... /usr/bin/install -c checking for ranlib... ranlib checking for ar... /usr/bin/ar checking for cp... /bin/cp checking for ln... /bin/ln checking for mkdir... /bin/mkdir checking for nroff... no checking for groff... no checking for rm... /bin/rm checking for strdup... yes checking for vsnprintf... yes configure: creating ./config.status config.status: creating Makefile config.status: creating mxml.list config.status: creating mxml.pc config.status: creating config.h configure: Menuselect build configuration successfully completed make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect' gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect.o menuselect.c gcc -g -c -D_GNU_SOURCE -Wall -c -o strcompat.o strcompat.c gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect_curses.o menuselect_curses.c make[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -O -Wall -c mxml-attr.c gcc -O -Wall -c mxml-entity.c gcc -O -Wall -c mxml-file.c gcc -O -Wall -c mxml-index.c gcc -O -Wall -c mxml-node.c gcc -O -Wall -c mxml-search.c gcc -O -Wall -c mxml-set.c gcc -O -Wall -c mxml-private.c gcc -O -Wall -c mxml-string.c /bin/rm -f libmxml.a /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml -string.o a - mxml-attr.o a - mxml-entity.o a - mxml-file.o a - mxml-index.o a - mxml-node.o a - mxml-search.o a - mxml-set.o a - mxml-private.o a - mxml-string.o ranlib libmxml.a make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -o menuselect menuselect.o strcompat.o menuselect_curses.o mxml/libmxml.a mxml/libmxml.a -lncurses make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' Generating input for menuselect ... *********************************************************** The existing menuselect.makeopts file did not specify that 'zttool' should not be included. However, either some dependencies for this module were not found or a conflict exists. Either run 'make menuselect' or remove the existing menuselect.makeopts file to resolve this issue. *********************************************************** make: *** [menuselect.makeopts] Error 255 make: Leaving directory `/usr/src/astsrc/zaptel' make: *** [upgrade-acid] Error 2 root@walter:/usr/src/astsrc# -- I can handle complexity. It's the simple things that confound me. Open your mind, Read, Learn, Think, Apply. 73, from NPKT! http://www.hybotics.com - NEW main site Just because we can, does it follow that we should?