ar9170-fw
I tried to build the toolchain from an uptodate pull of the git
repository,
I am getting a sequence of errors when the build reach libssp.
My guess would be that libssp is not needed for the ar9170 firmware.
Is this correct and I would appreciate an easy suguestion to
disable it if so.
make[3]: Entering directory `/usr/src/ar9170-fw/toolchain/build/gcc/sh-elf/libssp' if/bin/bash ./libtool --tag=CC --mode=compile /usr/src/ar9170-fw/toolchain/build/gcc/./gcc/xgcc -B/usr/src/ar9170-fw/toolchain/build/gcc/./gcc/ -B/usr/src/ar9170-fw/toolchain/inst/sh-elf/bin/ -B/usr/src/ar9170-fw/toolchain/inst/sh-elf/lib/ -isystem /usr/src/ar9170-fw/toolchain/inst/sh-elf/include -isystem /usr/src/ar9170-fw/toolchain/inst/sh-elf/sys-include -DHAVE_CONFIG_H -I. -I/usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp -I. -Wall -O2 -g -g -O2 -MT ssp.lo -MD -MP -MF ".deps/ssp.Tpo" -c -o ssp.lo /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c; \
then mv -f ".deps/ssp.Tpo" ".deps/ssp.Plo"; else rm -f ".deps/ssp.Tpo"; exit 1; fi
libtool: compile:/usr/src/ar9170-fw/toolchain/build/gcc/./gcc/xgcc -B/usr/src/ar9170-fw/toolchain/build/gcc/./gcc/ -B/usr/src/ar9170-fw/toolchain/inst/sh-elf/bin/ -B/usr/src/ar9170-fw/toolchain/inst/sh-elf/lib/ -isystem /usr/src/ar9170-fw/toolchain/inst/sh-elf/include -isystem /usr/src/ar9170-fw/toolchain/inst/sh-elf/sys-include -DHAVE_CONFIG_H -I. -I/usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp -I. -Wall -O2 -g -g -O2 -MT ssp.lo -MD -MP -MF .deps/ssp.Tpo -c /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c -o ssp.o /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c: In function '__guard_setup':/usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:70: warning: implicit declaration of function 'open' /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:70: error: 'O_RDONLY' undeclared (first use in this function) /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:70: error: (Each undeclared identifier is reported only once /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:70: error: for each function it appears in.) /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:73: error: 'ssize_t' undeclared (first use in this function) /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:73: error: expected ';' before 'size' /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:75: warning: implicit declaration of function 'close' /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:76: error: 'size' undeclared (first use in this function) /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c: At top level:/usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:89: error: expected declaration specifiers or '...' before 'size_t' /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c: In function 'fail':/usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:100: error: 'O_WRONLY' undeclared (first use in this function) /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:104: error: 'size_t' undeclared (first use in this function) /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:104: error: expected ';' before 'progname_len' /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:107: error:
'progname_len' undeclared (first use in this function) /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:107: warning: implicit declaration of function 'strlen' /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:107: warning:
incompatible implicit declaration of built-in function 'strlen' /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:108: error: 'len' undeclared (first use in this function) /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:108: error: 'msg1len' undeclared (first use in this function) /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:109: warning: implicit declaration of function 'alloca' /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:109: warning:
incompatible implicit declaration of built-in function 'alloca' /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:111: warning: implicit declaration of function 'memcpy' /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:111: warning:
incompatible implicit declaration of built-in function 'memcpy' /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:119: error: 'ssize_t' undeclared (first use in this function) /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:119: error: expected ';' before 'wrote' /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:120: error: 'wrote' undeclared (first use in this function) /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:151: warning: implicit declaration of function '_exit' /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:151: warning:
incompatible implicit declaration of built-in function '_exit' /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c: In function '__stack_chk_fail':/usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:161: warning:
incompatible implicit declaration of built-in function 'strlen' /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:161: warning: passing argument 2 of 'fail' makes pointer from integer without a cast /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:161: error: too many arguments to function 'fail' /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c: In function '__chk_fail':/usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:168: warning:
incompatible implicit declaration of built-in function 'strlen' /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:168: warning: passing argument 2 of 'fail' makes pointer from integer without a cast /usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:168: error: too many arguments to function 'fail'
make[3]: *** [ssp.lo] Error 1
make[3]: Leaving directory `/usr/src/ar9170-fw/toolchain/build/gcc/sh-elf/libssp' make[2]: *** [install-target-libssp] Error 2
make[2]: Leaving directory `/usr/src/ar9170-fw/toolchain/build/gcc' make[1]: *** [install] Error 2
make[1]: Leaving directory `/usr/src/ar9170-fw/toolchain/build/gcc'
make: *** [gcc] Error 2
Signature · 7 lines
Dave Lynch DLA Systems Software Development: Embedded Linux 717.587.7774 [email protected] http://www.dlasys.net Over 25 years' experience in platforms, languages, and technologies too numerous to list. "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." Albert Einstein
Hi
Quoted 11 lines · David H. Lynch Jr.
I tried to build the toolchain from an uptodate pull of the git
repository,I am getting a sequence of errors when the build reach libssp.
My guess would be that libssp is not needed for the ar9170 firmware.
Is this correct and I would appreciate an easy suguestion to
disable it if so.make[3]: Entering directory `/usr/src/ar9170-fw/toolchain/build/gcc/sh-elf/libssp'
[...]
Quoted 9 lines
-I/usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp -I. -Wall -O2 -g -g -O2 -MT ssp.lo -MD -MP -MF .deps/ssp.Tpo -c
/usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c-o ssp.o/usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c: In function '__guard_setup':/usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:70: warning: implicit declaration of function 'open'/usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:70: error: 'O_RDONLY' undeclared (first use in this function)
[...]
I assume your host's /bin/sh is not bash.
---------------------------------------------------------------------------
ar9170.fw: fix bashisms while building the cross toolchain.
toolchain/Makefile +2 -1
@@ -31,7 +31,8 @@ src/newlib-$(NEWLIB_VER): src/$(NEWLIB_T src/gcc-$(GCC_VER): src/$(GCC_TAR) src/newlib-$(NEWLIB_VER) tar -C src -xjf $< - ln -s $(BASEDIR)/src/newlib-$(NEWLIB_VER)/{newlib,libgloss} $@ + ln -s $(BASEDIR)/src/newlib-$(NEWLIB_VER)/newlib $@ + ln -s $(BASEDIR)/src/newlib-$(NEWLIB_VER)/libgloss $@ binutils: src/binutils-$(BINUTILS_VER) mkdir -p build/binutils
---------------------------------------------------------------------------
While you're at it, I'd suggest to bump the versions for the required cross-build environment as well, as it noticably improves stability of the firmware images built by it (still not perfectly, but better).
---------------------------------------------------------------------------
ar9170.fw: update cross-toolchain.
Updating the toolchain improves stability of the built firmware images significantly.
* gcc-4.4.4
* binutils-2.20.1
* newlib 1.18.0
toolchain/Makefile +3 -3
@@ -1,12 +1,12 @@ -BINUTILS_VER=2.19.1 +BINUTILS_VER=2.20.1 BINUTILS_URL=http://mirrors.kernel.org/gnu/binutils/binutils-$(BINUTILS_VER).tar.bz2 BINUTILS_TAR=binutils-$(BINUTILS_VER).tar.bz2 -NEWLIB_VER=1.17.0 +NEWLIB_VER=1.18.0 NEWLIB_URL=ftp://sources.redhat.com/pub/newlib/newlib-$(NEWLIB_VER).tar.gz NEWLIB_TAR=newlib-$(NEWLIB_VER).tar.gz -GCC_VER=4.3.3 +GCC_VER=4.4.4 GCC_URL=http://mirrors.kernel.org/gnu/gcc/gcc-$(GCC_VER)/gcc-core-$(GCC_VER).tar.bz2 GCC_TAR=gcc-core-$(GCC_VER).tar.bz2
---------------------------------------------------------------------------
Regards
Stefan Lippers-Hollmann
Johannes Berg
AppliedHi,
Quoted 2 lines
Quoted 2 lines
I tried to build the toolchain from an uptodate pull of the git
repository,
Not sure if that's still my repository, but
Quoted 3 lines
ar9170.fw: fix bashisms while building the cross toolchain.
ar9170.fw: update cross-toolchain.
I applied both your patches to it.
johannes
Quoted 4 lines · Stefan Lippers-Hollmann
Hi
I assume your host's
/bin/shis not bash.
ubuntu default
ls -al /bin/sh
lrwxrwxrwx 1 root root 4 2010-04-02 01:25 sh -> dash
I have bumped into similar problems with buildroot.
Is there a serious downside to linking /bin/sh to bash ?
Quoted 61 lines
---------------------------------------------------------------------------
ar9170.fw: fix bashisms while building the cross toolchain.
Signed-off-by Stefan Lippers-Hollmann<[email protected]>toolchain/Makefile +2
-2@@ -31,7 +31,8 @@ src/newlib-$(NEWLIB_VER): src/$(NEWLIB_T src/gcc-$(GCC_VER): src/$(GCC_TAR) src/newlib-$(NEWLIB_VER) tar -C src -xjf $< - ln -s $(BASEDIR)/src/newlib-$(NEWLIB_VER)/{newlib,libgloss} $@ + ln -s $(BASEDIR)/src/newlib-$(NEWLIB_VER)/newlib $@ + ln -s $(BASEDIR)/src/newlib-$(NEWLIB_VER)/libgloss $@ binutils: src/binutils-$(BINUTILS_VER) mkdir -p build/binutils ---------------------------------------------------------------------------While you're at it, I'd suggest to bump the versions for the required cross-build environment as well, as it noticably improves stability of the firmware images built by it (still not perfectly, but better).
---------------------------------------------------------------------------
ar9170.fw: update cross-toolchain.
Updating the toolchain improves stability of the built firmware images significantly.
* gcc-4.4.4
* binutils-2.20.1
* newlib 1.18.0Signed-off-by Stefan Lippers-Hollmann<[email protected]>toolchain/Makefile +3
-4@@ -1,12 +1,12 @@ -BINUTILS_VER=2.19.1 +BINUTILS_VER=2.20.1 BINUTILS_URL=http://mirrors.kernel.org/gnu/binutils/binutils-$(BINUTILS_VER).tar.bz2 BINUTILS_TAR=binutils-$(BINUTILS_VER).tar.bz2 -NEWLIB_VER=1.17.0 +NEWLIB_VER=1.18.0 NEWLIB_URL=ftp://sources.redhat.com/pub/newlib/newlib-$(NEWLIB_VER).tar.gz NEWLIB_TAR=newlib-$(NEWLIB_VER).tar.gz -GCC_VER=4.3.3 +GCC_VER=4.4.4 GCC_URL=http://mirrors.kernel.org/gnu/gcc/gcc-$(GCC_VER)/gcc-core-$(GCC_VER).tar.bz2 GCC_TAR=gcc-core-$(GCC_VER).tar.bz2 ---------------------------------------------------------------------------Regards
Stefan Lippers-Hollmann
Signature · 7 lines
Dave Lynch DLA Systems Software Development: Embedded Linux 717.587.7774 [email protected] http://www.dlasys.net Over 25 years' experience in platforms, languages, and technologies too numerous to list. "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." Albert Einstein
Did a git pull and picked up the bashisms and versions update.
At HEAD I get build failures in bfd
----------------------------------
make[5]: Entering directory `/usr/src/ar9170-fw/toolchain/build/binutils/bfd'
1011 /bin/sh ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I/usr/src/ar9170-fw/toolchain/src/binutils-2.20.1/bfd 1012 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/usr/src/ar9170-fw/toolchain/src/binutils-2.20.1/bfd -I. -I/usr/src/ar9170-fw/ 1013 cc1: warnings being treated as errors
1014 In file included from /usr/src/ar9170-fw/toolchain/src/binutils-2.20.1/bfd/elf32-sh.c:6055:
1015 ./elf32-target.h:718: error: initialization makes pointer from integer without a cast
1016 ./elf32-target.h:731: error: large integer implicitly truncated to unsigned type
1017 ./elf32-target.h:738: error: missing initializer
1018 ./elf32-target.h:738: error: (near initialization for ‘elf32_bed.want_p_paddr_set_to_zero’)
1019 ./elf32-target.h:826: error: ‘bfd_elf32_bfd_define_common_symbol’ undeclared here (not in a function) 1020 In file included from /usr/src/ar9170-fw/toolchain/src/binutils-2.20.1/bfd/elf32-sh.c:6074:
------------------------------------
If I back off todc858db5b191d70362d30f90906d68c1c3c2c972
the bashism fixes I get the same build errors in libssp in my first email.
In an unrelated toolchain build project (buildroot for a ppc405) I get libssp errors if I enable SSP.
I am reading the errors is a failure to properly include standard headers.
I am working under ubuntu lucid
gcc --ver as follows:
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.4.3-4ubuntu5' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --enable-multiarch --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4 --program-suffix=-4.4 --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-plugin --enable-objc-gc --enable-targets=all --disable-werror --with-arch-32=i486 --with-tune=generic --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu Thread model: posix
gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5)
Alternately maybe I am missing some development dependency that configure is not warning about
Quoted 97 lines · Stefan Lippers-Hollmann
Hi
Quoted 12 lines · David H. Lynch Jr.
I tried to build the toolchain from an uptodate pull of the git
repository,I am getting a sequence of errors when the build reach libssp.
My guess would be that libssp is not needed for the ar9170 firmware.
Is this correct and I would appreciate an easy suguestion to
disable it if so.make[3]: Entering directory `/usr/src/ar9170-fw/toolchain/build/gcc/sh-elf/libssp'
[...]
Quoted 10 lines
-I/usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp -I. -Wall -O2 -g -g -O2 -MT ssp.lo -MD -MP -MF .deps/ssp.Tpo -c
/usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c-o ssp.o/usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c: In function '__guard_setup':/usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:70: warning: implicit declaration of function 'open'/usr/src/ar9170-fw/toolchain/src/gcc-4.3.3/libssp/ssp.c:70: error: 'O_RDONLY' undeclared (first use in this function)[...]
I assume your host's
/bin/shis not bash.---------------------------------------------------------------------------
ar9170.fw: fix bashisms while building the cross toolchain.
Signed-off-by Stefan Lippers-Hollmann<[email protected]>toolchain/Makefile +2
-2@@ -31,7 +31,8 @@ src/newlib-$(NEWLIB_VER): src/$(NEWLIB_T src/gcc-$(GCC_VER): src/$(GCC_TAR) src/newlib-$(NEWLIB_VER) tar -C src -xjf $< - ln -s $(BASEDIR)/src/newlib-$(NEWLIB_VER)/{newlib,libgloss} $@ + ln -s $(BASEDIR)/src/newlib-$(NEWLIB_VER)/newlib $@ + ln -s $(BASEDIR)/src/newlib-$(NEWLIB_VER)/libgloss $@ binutils: src/binutils-$(BINUTILS_VER) mkdir -p build/binutils ---------------------------------------------------------------------------While you're at it, I'd suggest to bump the versions for the required cross-build environment as well, as it noticably improves stability of the firmware images built by it (still not perfectly, but better).
---------------------------------------------------------------------------
ar9170.fw: update cross-toolchain.
Updating the toolchain improves stability of the built firmware images significantly.
* gcc-4.4.4
* binutils-2.20.1
* newlib 1.18.0Signed-off-by Stefan Lippers-Hollmann<[email protected]>toolchain/Makefile +3
-4@@ -1,12 +1,12 @@ -BINUTILS_VER=2.19.1 +BINUTILS_VER=2.20.1 BINUTILS_URL=http://mirrors.kernel.org/gnu/binutils/binutils-$(BINUTILS_VER).tar.bz2 BINUTILS_TAR=binutils-$(BINUTILS_VER).tar.bz2 -NEWLIB_VER=1.17.0 +NEWLIB_VER=1.18.0 NEWLIB_URL=ftp://sources.redhat.com/pub/newlib/newlib-$(NEWLIB_VER).tar.gz NEWLIB_TAR=newlib-$(NEWLIB_VER).tar.gz -GCC_VER=4.3.3 +GCC_VER=4.4.4 GCC_URL=http://mirrors.kernel.org/gnu/gcc/gcc-$(GCC_VER)/gcc-core-$(GCC_VER).tar.bz2 GCC_TAR=gcc-core-$(GCC_VER).tar.bz2 ---------------------------------------------------------------------------Regards
Stefan Lippers-Hollmann
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 7 lines
Dave Lynch DLA Systems Software Development: Embedded Linux 717.587.7774 [email protected] http://www.dlasys.net Over 25 years' experience in platforms, languages, and technologies too numerous to list. "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." Albert Einstein
Hi
Quoted 37 lines · David H. Lynch Jr.
Did a git pull and picked up the bashisms and versions update.
At HEAD I get build failures in bfd----------------------------------
make[5]: Entering directory `/usr/src/ar9170-fw/toolchain/build/binutils/bfd'
1011/bin/sh./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I/usr/src/ar9170-fw/toolchain/src/binutils-2.20.1/bfd
1012 libtool: compile: gcc -DHAVE_CONFIG_H -I.(quoted diff) +0
-2-I/usr/src/ar9170-fw/toolchain/src/binutils-2.20.1/bfd -I. -I/usr/src/ar9170-fw/1013 cc1: warnings being treated as errors
1014 In file included from/usr/src/ar9170-fw/toolchain/src/binutils-2.20.1/bfd/elf32-sh.c:6055:
1015 ./elf32-target.h:718: error: initialization makes pointer from integer without a cast
1016 ./elf32-target.h:731: error: large integer implicitly truncated to unsigned type
1017 ./elf32-target.h:738: error: missing initializer
1018 ./elf32-target.h:738: error: (near initialization for ‘elf32_bed.want_p_paddr_set_to_zero’)
1019 ./elf32-target.h:826: error: ‘bfd_elf32_bfd_define_common_symbol’ undeclared here (not in a function)
1020 In file included from/usr/src/ar9170-fw/toolchain/src/binutils-2.20.1/bfd/elf32-sh.c:6074:
------------------------------------If I back off to
dc858db5b191d70362d30f90906d68c1c3c2c972
the bashism fixes I get the same build errors in libssp in my first email.In an unrelated toolchain build project (buildroot for a ppc405) I get libssp errors if I enable SSP.
I am reading the errors is a failure to properly include standard headers.
I am working under ubuntu lucid
[...]
Quoted 2 lines
Alternately maybe I am missing some development dependency that configure is not warning about
I have verified before sending the mail yesterday that ar9170.fw still builds fine on current Debian unstable (gcc-4.4, but it also worked on 4.4.2, 4.4.3 before; confirmed in a minimal build chroot (pbuilder) environment), so you're likely just missing build dependencies.
# apt-get install build-essential # apt-get build-dep gcc-4.4 binutils newlib
While this pulls a little more than you'd absolutely need, it still makes sure that all eventual build dependencies are covered.
Regards
Stefan Lippers-Hollmann