[asterisk-users] C compiler cannot create executables when building zaptel
CSB
kjcsb at xnet.co.nz
Thu Mar 6 11:22:16 CST 2008
> > I believe I have all the necessary packages installed.
> >
> > Having done some research, one link suggests using strace and in that
> case I
> > don't get the error:
> > strace -f -o /tmp/trace -e trace=process ./configure
> > ...
> > configure: *** Zaptel build successfully configured ***
>
> That's from the end of the configure script. Can you post your
> config.log ?
the config.log from strace -f -o /tmp/trace -e trace=process ./configure
configure:2066: $? = 0
configure:2073: gcc -v >&5
Using built-in specs.
Target: i386-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --enable-shared --enable-threads=posix
--enable-checking=release --with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-libgcj-multifile
--enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk
--disable-dssi --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre
--with-cpu=generic --host=i386-redhat-linux
Thread model: posix
gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)
configure:2076: $? = 0
configure:2083: gcc -V >&5
gcc: '-V' option must have argument
configure:2086: $? = 1
configure:2109: checking for C compiler default output file name
configure:2136: gcc conftest.c >&5
configure:2139: $? = 0
configure:2177: result: a.out
configure:2194: checking whether the C compiler works
configure:2204: ./a.out
configure:2207: $? = 0
configure:2224: result: yes
configure:2231: checking whether we are cross compiling
configure:2233: result: no
configure:2236: checking for suffix of executables
configure:2243: gcc -o conftest conftest.c >&5
configure:2246: $? = 0
configure:2270: result:
configure:2276: checking for suffix of object files
configure:2302: gcc -c conftest.c >&5
configure:2305: $? = 0
configure:2328: result: o
configure:2332: checking whether we are using the GNU C compiler
configure:2361: gcc -c conftest.c >&5
configure:2367: $? = 0
configure:2384: result: yes
configure:2389: checking whether gcc accepts -g
configure:2419: gcc -c -g conftest.c >&5
configure:2425: $? = 0
configure:2524: result: yes
configure:2541: checking for gcc option to accept ISO C89
configure:2615: gcc -c -g -O2 conftest.c >&5
configure:2621: $? = 0
configure:2644: result: none needed
configure:2667: checking how to run the C preprocessor
configure:2707: gcc -E conftest.c
configure:2713: $? = 0
configure:2744: gcc -E conftest.c
conftest.c:9:28: error: ac_nonexistent.h: No such file or directory
configure:2750: $? = 1
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define _GNU_SOURCE 1
| /* end confdefs.h. */
| #include <ac_nonexistent.h>
configure:2783: result: gcc -E
configure:2812: gcc -E conftest.c
configure:2818: $? = 0
configure:2849: gcc -E conftest.c
conftest.c:9:28: error: ac_nonexistent.h: No such file or directory
configure:2855: $? = 1
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define _GNU_SOURCE 1
| /* end confdefs.h. */
| #include <ac_nonexistent.h>
configure:2936: checking for a BSD-compatible install
configure:2992: result: /usr/bin/install -c
configure:3003: checking whether ln -s works
configure:3007: result: yes
configure:3014: checking for GNU make
configure:3029: result: make
configure:3055: gcc -c -g -O2 conftest.c >&5
configure:3061: $? = 0
configure:3087: checking for grep
configure:3105: found /bin/grep
configure:3118: result: /bin/grep
configure:3128: checking for sh
configure:3159: result: /bin/sh
configure:3169: checking for ln
configure:3187: found /bin/ln
configure:3200: result: /bin/ln
configure:3211: checking for wget
configure:3229: found /usr/bin/wget
configure:3242: result: /usr/bin/wget
configure:3306: checking for grep that handles long lines and -e
configure:3380: result: /bin/grep
configure:3385: checking for egrep
configure:3463: result: /bin/grep -E
configure:3468: checking for ANSI C header files
configure:3498: gcc -c -g -O2 conftest.c >&5
configure:3504: $? = 0
configure:3603: gcc -o conftest -g -O2 conftest.c >&5
configure:3606: $? = 0
configure:3612: ./conftest
configure:3615: $? = 0
configure:3632: result: yes
configure:3656: checking for sys/types.h
configure:3677: gcc -c -g -O2 conftest.c >&5
configure:3683: $? = 0
configure:3699: result: yes
configure:3656: checking for sys/stat.h
configure:3677: gcc -c -g -O2 conftest.c >&5
configure:3683: $? = 0
configure:3699: result: yes
configure:3656: checking for stdlib.h
configure:3677: gcc -c -g -O2 conftest.c >&5
configure:3683: $? = 0
configure:3699: result: yes
configure:3656: checking for string.h
configure:3677: gcc -c -g -O2 conftest.c >&5
configure:3683: $? = 0
configure:3699: result: yes
configure:3656: checking for memory.h
configure:3677: gcc -c -g -O2 conftest.c >&5
configure:3683: $? = 0
configure:3699: result: yes
configure:3656: checking for strings.h
configure:3677: gcc -c -g -O2 conftest.c >&5
configure:3683: $? = 0
configure:3699: result: yes
configure:3656: checking for inttypes.h
configure:3677: gcc -c -g -O2 conftest.c >&5
configure:3683: $? = 0
configure:3699: result: yes
configure:3656: checking for stdint.h
configure:3677: gcc -c -g -O2 conftest.c >&5
configure:3683: $? = 0
configure:3699: result: yes
configure:3656: checking for unistd.h
configure:3677: gcc -c -g -O2 conftest.c >&5
configure:3683: $? = 0
configure:3699: result: yes
configure:3739: checking for initscr in -lcurses
configure:3774: gcc -o conftest -g -O2 conftest.c -lcurses >&5
configure:3780: $? = 0
configure:3798: result: yes
configure:3962: checking curses.h usability
configure:3979: gcc -c -g -O2 conftest.c >&5
configure:3985: $? = 0
configure:3999: result: yes
configure:4003: checking curses.h presence
configure:4018: gcc -E conftest.c
configure:4024: $? = 0
configure:4038: result: yes
configure:4066: checking for curses.h
configure:4073: result: yes
configure:4155: checking for initscr in -lncurses
configure:4190: gcc -o conftest -g -O2 conftest.c -lncurses >&5
configure:4196: $? = 0
configure:4214: result: yes
configure:4369: checking for curses.h
configure:4374: result: yes
configure:4571: checking for newtBell in -lnewt
configure:4606: gcc -o conftest -g -O2 conftest.c -lnewt >&5
configure:4612: $? = 0
configure:4630: result: yes
configure:4794: checking newt.h usability
configure:4811: gcc -c -g -O2 conftest.c >&5
configure:4817: $? = 0
configure:4831: result: yes
configure:4835: checking newt.h presence
configure:4850: gcc -E conftest.c
configure:4856: $? = 0
configure:4870: result: yes
configure:4898: checking for newt.h
configure:4905: result: yes
configure:4987: checking for usb_init in -lusb
configure:5022: gcc -o conftest -g -O2 conftest.c -lusb >&5
configure:5028: $? = 0
configure:5046: result: yes
configure:5210: checking usb.h usability
configure:5227: gcc -c -g -O2 conftest.c >&5
configure:5233: $? = 0
configure:5247: result: yes
configure:5251: checking usb.h presence
configure:5266: gcc -E conftest.c
configure:5272: $? = 0
configure:5286: result: yes
configure:5314: checking for usb.h
configure:5321: result: yes
configure:5573: creating ./config.status
## ---------------------- ##
## Running config.status. ##
## ---------------------- ##
This file was extended by config.status, which was
generated by GNU Autoconf 2.61. Invocation command line was
CONFIG_FILES =
CONFIG_HEADERS =
CONFIG_LINKS =
CONFIG_COMMANDS =
$ ./config.status
on beta.domain.com
config.status:604: creating build_tools/menuselect-deps
config.status:604: creating makeopts
config.status:604: creating build_tools/make_firmware_object
configure:6486: *** Zaptel build successfully configured ***
>
> >
> > uname -a
> > Linux beta.domain.com 2.6.20-1.2320.fc5 #1 Tue Jun 12 18:50:38 EDT
> 2007 i686
> > i686 i386 GNU/Linux
> >
> > Could anyone suggest why this is the case?
>
> What version of Zaptel is it?
zaptel-1.4.9.1
>
> What is the output of:
>
> ./install_prereq test
#############################################
## test: test mode.
## Use the commands here to install your system.
#############################################
#############################################
## test completed successfully
## (in test mode)
#############################################
>
More information about the asterisk-users
mailing list