Hi All,
I'm new to the community and I was trying to compile openwrt trunk branch for an atheros device but without success.....
Probably, there is a bug in the build system or in my environment....
I'm using Ubuntu 7.10 under VmWare on a Windows XP system.
I've already installed all the needed packages (newest version):
gcc, g++, binutils, patch, bzip2, flex, bison, make, gettext, unzip, ncurses (libncurses-dev), libz-dev and
libc headers -- additional package dependencies: madwifi: uudecode(sharutils), privoxy: autoconf pkg-config automake (see FAQ)
Anyway, It seems that I'm not able to build the toolchain (or something else) :-(
This is an extract of config.log :
configure:2151: $? = 0
configure:2153: gcc -v </dev/null >&5
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v --enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.1.3 --program-suffix=-4.1 --enable-__cxa_atexit --enable-clocale=gnu --enable-libstdcxx-debug --enable-mpfr --enable-checking=release i486-linux-gnu
Thread model: posix
gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)
configure:2156: $? = 0
configure:2158: gcc -V </dev/null >&5
gcc: '-V' option must have argument
configure:2161: $? = 1
configure:2184: checking for C compiler default output file name
configure:2187: gcc -g -O2 conftest.c >&5
/home/jars/Development/trunk/staging_dir/toolchain-mips_gcc4.1.2/bin/mips-linux-uclibc-as: unrecognized option `-Qy'
configure:2190: $? = 1
configure: failed program was:
| /* confdefs.h. */
|
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:2228: error: C compiler cannot create executables
See `config.log' for more details.
The assembler doesn't like the -Qy option....
I found in the trac that somebody else had a similar problem https://dev.openwrt.org/ticket/2800 solved with https://dev.openwrt.org/changeset/9717 therefore it seems strange that it is happening again...there's been a regression problem on some file or it is a wrong build environment??
Should I start from a particular revision to solve???
Any hint is welcome because I'm not able to go further....
Sorry for long post
Thank you
Carlo