[Buildroot] AVR32 4.1.2 toolchain build issues [was svn commit: trunk/buildroot: target/device target/device/Atmel target etc...]

[Buildroot] AVR32 4.1.2 toolchain build issues [was svn commit: trunk/buildroot: target/device target/device/Atmel target etc...]

[Thiago A. Corrêa]

Hi,

   I thought it was best to split into a new thread, relates to this
thread: http://buildroot.uclibc.org/lists/buildroot/2007-October/005792.html

   That commit introduced gcc 4.2.1 to avr32, which builds ok, but the
compiler still has some bugs, specially the C++ compiler and the
template engine.

   Now I'm trying to get 4.1.2 to build. Previously we had the cryptic
GCC_NO_EXECUTABLES issue during libstdc++-v3 configure. Now, a bit
down the road, I have some install error:

 /bin/sh ../libtool --mode=install /usr/bin/install -c  'libsupc++.la'
'/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/avr32-linux-uclibc/lib/libsupc++.la'
 /usr/bin/install -c -m 644
/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-avr32-2.0/libstdc++-v3/libsupc++/new
/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/include/c++/4.1.2/new
 /usr/bin/install -c -m 644
/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-avr32-2.0/libstdc++-v3/libsupc++/typeinfo
/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/include/c++/4.1.2/typeinfo
 /usr/bin/install -c -m 644
/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-avr32-2.0/libstdc++-v3/libsupc++/cxxabi.h
/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/include/c++/4.1.2/cxxabi.h
 /usr/bin/install -c -m 644
/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-avr32-2.0/libstdc++-v3/libsupc++/exception_defines.h
/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/include/c++/4.1.2/exception_defines.h
/usr/bin/install -c .libs/libsupc++.lai
/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/avr32-linux-uclibc/lib/libsupc++.la
/usr/bin/install -c .libs/libsupc++.a
/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/avr32-linux-uclibc/lib/libsupc++.a

chmod 644 /root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/avr32-linux-uclibc/lib/libsupc++.a
/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/usr/bin/avr32-linux-uclibc-ranlib
/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/avr32-linux-uclibc/lib/libsupc++.a
PATH="$PATH:/sbin" ldconfig -n
/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/avr32-linux-uclibc/lib
----------------------------------------------------------------------
Libraries have been installed in:
   /root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/avr32-linux-uclibc/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
     during execution
   - add LIBDIR to the `LD_RUN_PATH' environment variable
     during linking
   - use the `-Wl,--rpath -Wl,LIBDIR' linker flag
   - have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
make[5]: Leaving directory
`/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/avr32-linux-uclibc/libstdc++-v3/libsupc++'
make[4]: Leaving directory
`/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/avr32-linux-uclibc/libstdc++-v3/libsupc++'
Making install in libmath
make[4]: Entering directory
`/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/avr32-linux-uclibc/libstdc++-v3/libmath'
make[5]: Entering directory
`/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/avr32-linux-uclibc/libstdc++-v3/libmath'
make[5]: Nothing to be done for `install-exec-am'.
make[5]: Nothing to be done for `install-data-am'.
make[5]: Leaving directory
`/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/avr32-linux-uclibc/libstdc++-v3/libmath'
make[4]: Leaving directory
`/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/avr32-linux-uclibc/libstdc++-v3/libmath'
Making install in src
make[4]: Entering directory
`/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/avr32-linux-uclibc/libstdc++-v3/src'
make[5]: Entering directory
`/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/avr32-linux-uclibc/libstdc++-v3/src'
test -z "/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/avr32-linux-uclibc/lib"
|| mkdir -p -- "/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/avr32-linux-uclibc/lib"
/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/usr/bin/avr32-linux-uclibc-ar
cru libstdc++_pic.a *.o ../libsupc++/*.o
make[5]: Nothing to be done for `install-data-am'.
 /bin/sh ../libtool --mode=install /usr/bin/install -c  'libstdc++.la'
'/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/avr32-linux-uclibc/lib/libstdc++.la'
/usr/bin/install -c -m 644 libstdc++_pic.a
/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/avr32-linux-uclibc/lib
/usr/bin/install -c .libs/libstdc++.so.6.0.8
/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/avr32-linux-uclibc/lib/libstdc++.so.6.0.8
(cd /root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/avr32-linux-uclibc/lib
&& rm -f libstdc++.so.6 && ln -s libstdc++.so.6.0.8 libstdc++.so.6)
(cd /root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/avr32-linux-uclibc/lib
&& rm -f libstdc++.so && ln -s libstdc++.so.6.0.8 libstdc++.so)
/usr/bin/install -c .libs/libstdc++.lai
/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/avr32-linux-uclibc/lib/libstdc++.la
/usr/bin/install -c .libs/libstdc++.a
/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/avr32-linux-uclibc/lib/libstdc++.a

chmod 644 /root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/avr32-linux-uclibc/lib/libstdc++.a
/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/usr/bin/avr32-linux-uclibc-ranlib
/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/avr32-linux-uclibc/lib/libstdc++.a
PATH="$PATH:/sbin" ldconfig -n
/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/avr32-linux-uclibc/lib
----------------------------------------------------------------------
Libraries have been installed in:
   /root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/avr32-linux-uclibc/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
     during execution
   - add LIBDIR to the `LD_RUN_PATH' environment variable
     during linking
   - use the `-Wl,--rpath -Wl,LIBDIR' linker flag
   - have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
make[5]: Leaving directory
`/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/avr32-linux-uclibc/libstdc++-v3/src'
make[4]: Leaving directory
`/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/avr32-linux-uclibc/libstdc++-v3/src'
Making install in po
make[4]: Entering directory
`/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/avr32-linux-uclibc/libstdc++-v3/po'
make[5]: Entering directory
`/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/avr32-linux-uclibc/libstdc++-v3/po'
make[5]: Nothing to be done for `install-exec-am'.
make[5]: Nothing to be done for `install-data-am'.
make[5]: Leaving directory
`/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/avr32-linux-uclibc/libstdc++-v3/po'
make[4]: Leaving directory
`/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/avr32-linux-uclibc/libstdc++-v3/po'
Making install in testsuite
make[4]: Entering directory
`/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/avr32-linux-uclibc/libstdc++-v3/testsuite'
make[5]: Entering directory
`/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/avr32-linux-uclibc/libstdc++-v3/testsuite'
make[5]: warning: -jN forced in submake: disabling jobserver mode.
make[5]: Nothing to be done for `install-exec-am'.
make[5]: Nothing to be done for `install-data-am'.
make[5]: Leaving directory
`/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/avr32-linux-uclibc/libstdc++-v3/testsuite'
make[4]: Leaving directory
`/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/avr32-linux-uclibc/libstdc++-v3/testsuite'
make[4]: Entering directory
`/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/avr32-linux-uclibc/libstdc++-v3'
true "AR_FLAGS=rc" "CC_FOR_BUILD=/usr/bin/gcc"
"CC_FOR_TARGET=/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/usr/bin/avr32-linux-uclibc-gcc"
"CFLAGS=-g -Os" "CXXFLAGS=-g -Os" "CFLAGS_FOR_BUILD="
"CFLAGS_FOR_TARGET=-g -Os" "INSTALL=/usr/bin/install -c"
"INSTALL_DATA=/usr/bin/install -c -m 644"
"INSTALL_PROGRAM=/usr/bin/install -c" "INSTALL_SCRIPT=/usr/bin/install
-c" "LDFLAGS=LDFLAGS+=-Wl,-L/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/lib
LDFLAGS+=-Wl,-L/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/usr/lib
-L/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/lib
-L/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/usr/lib"
"LIBCFLAGS=-g -Os" "LIBCFLAGS_FOR_TARGET=-g -Os" "MAKE=/usr/bin/make"
"MAKEINFO=makeinfo --split-size=5000000 --split-size=5000000  "
"PICFLAG=" "PICFLAG_FOR_TARGET=" "SHELL=/bin/sh" "RUNTESTFLAGS="
"exec_prefix=/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir"
"infodir=/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/info"
"libdir=/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/lib"
"includedir=/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/include"
"prefix=/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir"
"tooldir=/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/avr32-linux-uclibc"
"gxx_include_dir=/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/include/c++/4.1.2"
"AR=/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/usr/bin/avr32-linux-uclibc-ar"
"AS=/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/./gcc/as"
"LD=/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/./gcc/collect-ld"
"RANLIB=/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/usr/bin/avr32-linux-uclibc-ranlib"
"NM=/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/./gcc/nm"
"NM_FOR_BUILD="
"NM_FOR_TARGET=/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/usr/bin/avr32-linux-uclibc-nm"
"DESTDIR=" "WERROR=" DO=all multi-do # /usr/bin/make
make[5]: Entering directory
`/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/avr32-linux-uclibc/libstdc++-v3'
true "AR_FLAGS=rc" "CC_FOR_BUILD=/usr/bin/gcc"
"CC_FOR_TARGET=/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/usr/bin/avr32-linux-uclibc-gcc"
"CFLAGS=-g -Os" "CXXFLAGS=-g -Os" "CFLAGS_FOR_BUILD="
"CFLAGS_FOR_TARGET=-g -Os" "INSTALL=/usr/bin/install -c"
"INSTALL_DATA=/usr/bin/install -c -m 644"
"INSTALL_PROGRAM=/usr/bin/install -c" "INSTALL_SCRIPT=/usr/bin/install
-c" "LDFLAGS=LDFLAGS+=-Wl,-L/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/lib
LDFLAGS+=-Wl,-L/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/usr/lib
-L/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/lib
-L/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/usr/lib"
"LIBCFLAGS=-g -Os" "LIBCFLAGS_FOR_TARGET=-g -Os" "MAKE=/usr/bin/make"
"MAKEINFO=makeinfo --split-size=5000000 --split-size=5000000   "
"PICFLAG=" "PICFLAG_FOR_TARGET=" "SHELL=/bin/sh" "RUNTESTFLAGS="
"exec_prefix=/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir"
"infodir=/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/info"
"libdir=/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/lib"
"includedir=/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/include"
"prefix=/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir"
"tooldir=/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/avr32-linux-uclibc"
"gxx_include_dir=/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/include/c++/4.1.2"
"AR=/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/usr/bin/avr32-linux-uclibc-ar"
"AS=/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/./gcc/as"
"LD=/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/./gcc/collect-ld"
"RANLIB=/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/usr/bin/avr32-linux-uclibc-ranlib"
"NM=/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/./gcc/nm"
"NM_FOR_BUILD="
"NM_FOR_TARGET=/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/usr/bin/avr32-linux-uclibc-nm"
"DESTDIR=" "WERROR=" DO=install multi-do # /usr/bin/make
make[5]: Nothing to be done for `install-data-am'.
make[5]: Leaving directory
`/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/avr32-linux-uclibc/libstdc++-v3'
make[4]: Leaving directory
`/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/avr32-linux-uclibc/libstdc++-v3'
make[3]: Leaving directory
`/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/avr32-linux-uclibc/libstdc++-v3'
make[2]: Leaving directory
`/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final'
make[1]: *** [install] Error 2
make[1]: Leaving directory
`/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final'
make: *** [/root/novacomm/buildroot/buildroot-original/toolchain_build_avr32/gcc-4.1.2-final/.installed]
Error 2


Sorry for all of the verbosity, but I can't make much sense out of
those make errors. For one, I can never quite tell exactly which step
failed.

[Buildroot] AVR32 4.1.2 toolchain build issues [was svn commit:trunk/buildroot: target/device target/device/Atmel target etc...]

[Ulf Samuelsson]

>   That commit introduced gcc 4.2.1 to avr32, which builds ok, but the
> compiler still has some bugs, specially the C++ compiler and the
> template engine.


I tested with

make atngw100_defconfig
make

which manages to build both the linux and the root fs.

atstk1002_defconfig has not been tested yet.


Best Regards
Ulf Samuelsson                ulf at atmel.com
Atmel Nordic AB
Mail:  Box 2033, 174 02 Sundbyberg, Sweden
Visit:  Kavalleriv?gen 24, 174 58 Sundbyberg, Sweden
Phone +46 (8) 441 54 22     Fax +46 (8) 441 54 29
GSM    +46 (706) 22 44 57 

[Buildroot] AVR32 4.1.2 toolchain build issues [was svn commit:trunk/buildroot: target/device target/device/Atmel target etc...]

[don]

On Mon, Oct 15, 2007 at 11:25:52PM +0200, Ulf Samuelsson wrote:
>>   That commit introduced gcc 4.2.1 to avr32, which builds ok, but the
>> compiler still has some bugs, specially the C++ compiler and the
>> template engine.
>
>
> I tested with
>
> make atngw100_defconfig
> make
>
> which manages to build both the linux and the root fs.

It failed for me twice.  First with the libtool error I posted
recently, then in uboot.  

...
rm -rf /home/dev/AVR32/Buildroot/buildroot/project_build_avr32/atngw100/buildroot-config
mkdir -p /home/dev/AVR32/Buildroot/buildroot/project_build_avr32/atngw100
cp -dpRf package/config/buildroot-config /home/dev/AVR32/Buildroot/buildroot/project_build_avr32/atngw100/buildroot-config
cp target/device/Atmel/atngw100/u-boot/atngw100.h /home/dev/AVR32/Buildroot/buildroot/build_avr32/u-boot-1.2.0-atmel/include/configs/.
cp: cannot stat `target/device/Atmel/atngw100/u-boot/atngw100.h': No such file or directory
...

-- 
Don

[Buildroot] AVR32 4.1.2 toolchain build issues [was svncommit:trunk/buildroot: target/device target/device/Atmel targetetc...]

[Ulf Samuelsson]

link: www.avrfreaks.net
----- Original Message ----- 
From: "don" <don_reid@comcast.net>
To: "Ulf Samuelsson" <ulf@atmel.com>
Cc: "Thiago A. Corr?a" <thiago.correa@gmail.com>; <buildroot@uclibc.org>
Sent: Tuesday, October 16, 2007 12:17 AM
Subject: Re: [Buildroot] AVR32 4.1.2 toolchain build issues [was 
svncommit:trunk/buildroot: target/device target/device/Atmel targetetc...]


> On Mon, Oct 15, 2007 at 11:25:52PM +0200, Ulf Samuelsson wrote:
>>>   That commit introduced gcc 4.2.1 to avr32, which builds ok, but the
>>> compiler still has some bugs, specially the C++ compiler and the
>>> template engine.
>>
>>
>> I tested with
>>
>> make atngw100_defconfig
>> make
>>
>> which manages to build both the linux and the root fs.
>
> It failed for me twice.  First with the libtool error I posted
> recently, then in uboot.
>
> ...
> rm -rf 
> /home/dev/AVR32/Buildroot/buildroot/project_build_avr32/atngw100/buildroot-config
> mkdir -p /home/dev/AVR32/Buildroot/buildroot/project_build_avr32/atngw100
> cp -dpRf package/config/buildroot-config 
> /home/dev/AVR32/Buildroot/buildroot/project_build_avr32/atngw100/buildroot-config
> cp target/device/Atmel/atngw100/u-boot/atngw100.h 
> /home/dev/AVR32/Buildroot/buildroot/build_avr32/u-boot-1.2.0-atmel/include/configs/.
> cp: cannot stat `target/device/Atmel/atngw100/u-boot/atngw100.h': No such 
> file or directory
> ...
>
> -- 
> Don


Don't know why the libtool stuff fails, but the u-boot was never supported 
for ngw100.
It might be as simple as adding the file:

target/device/Atmel/atngw100/u-boot/ngw100.h

The file will come from the (latest) u-boot source 
"include/configs/ngw100.h"

Is U-Boot on by default?
Maybe I turned it off, before I built it.

There is a later u-boot at the u-boot home page.


Best Regards
Ulf Samuelsson

[Buildroot] AVR32 4.1.2 toolchain build issues [was svncommit:trunk/buildroot: target/device target/device/Atmel targetetc...]

[don]

On Tue, Oct 16, 2007 at 12:22:03AM +0200, Ulf Samuelsson wrote:
> link: www.avrfreaks.net
> ----- Original Message ----- From: "don" <don_reid@comcast.net>
> To: "Ulf Samuelsson" <ulf@atmel.com>
> Cc: "Thiago A. Corr?a" <thiago.correa@gmail.com>; <buildroot@uclibc.org>
> Sent: Tuesday, October 16, 2007 12:17 AM
> Subject: Re: [Buildroot] AVR32 4.1.2 toolchain build issues [was 
> svncommit:trunk/buildroot: target/device target/device/Atmel targetetc...]
>
>
>> On Mon, Oct 15, 2007 at 11:25:52PM +0200, Ulf Samuelsson wrote:
>>>>   That commit introduced gcc 4.2.1 to avr32, which builds ok, but the
>>>> compiler still has some bugs, specially the C++ compiler and the
>>>> template engine.
>>>
>>>
>>> I tested with
>>>
>>> make atngw100_defconfig
>>> make
>>>
>>> which manages to build both the linux and the root fs.
>>
>> It failed for me twice.  First with the libtool error I posted
>> recently, then in uboot.
>>
>> ...
>> rm -rf 
>> /home/dev/AVR32/Buildroot/buildroot/project_build_avr32/atngw100/buildroot-config
>> mkdir -p /home/dev/AVR32/Buildroot/buildroot/project_build_avr32/atngw100
>> cp -dpRf package/config/buildroot-config 
>> /home/dev/AVR32/Buildroot/buildroot/project_build_avr32/atngw100/buildroot-config
>> cp target/device/Atmel/atngw100/u-boot/atngw100.h 
>> /home/dev/AVR32/Buildroot/buildroot/build_avr32/u-boot-1.2.0-atmel/include/configs/.
>> cp: cannot stat `target/device/Atmel/atngw100/u-boot/atngw100.h': No such 
>> file or directory
>> ...
>>
>> -- 
>> Don
>
>
> Don't know why the libtool stuff fails, but the u-boot was never supported 
> for ngw100.
> It might be as simple as adding the file:
>
> ...
>
> Is U-Boot on by default?
> Maybe I turned it off, before I built it.
>
> There is a later u-boot at the u-boot home page.

I just did a clean buildroot checkout and then

	make atngw100_defconfig
	make

If U-Boot shouldn't be build for the atngw100_defconfig then that
config should turn it off.

-- 
Don

[Buildroot] AVR32 4.1.2 toolchain build issues [was svncommit:trunk/buildroot: target/device target/device/Atmel targetetc...]

[Thiago A. Corrêa]

Ok.... got it to build... it happens to be that atngw100_defconfig now
builds to a dir without nofp sufix, which makes me wonder if ppl have
decided weather this thing has or doesn't has an FP, perhaps it's a
paradox, or a dogma. You just have to belive it works. *smile*

Anyway, disabled libdaemon, which I never use anyway, and now I get
the uboot issue as well.... but at least I can work now. It should be
easily enough to pull uboot from the Atmel AVR32 fork and figure out
what's wrong. Dealing with packages is so much easier.

Btw, is there a reason why u-boot is buried into Atmel folder?
Shouldn't other archs/chips use it as well?

Hopefully I will come back with patches once more (have a better
qtopia building, in a single stage, on the works).

Friendly Regards,
    Thiago A. Correa



On 10/16/07, don <don_reid@comcast.net> wrote:
> On Tue, Oct 16, 2007 at 12:22:03AM +0200, Ulf Samuelsson wrote:
> > link: www.avrfreaks.net
> > ----- Original Message ----- From: "don" <don_reid@comcast.net>
> > To: "Ulf Samuelsson" <ulf@atmel.com>
> > Cc: "Thiago A. Corr?a" <thiago.correa@gmail.com>; <buildroot@uclibc.org>
> > Sent: Tuesday, October 16, 2007 12:17 AM
> > Subject: Re: [Buildroot] AVR32 4.1.2 toolchain build issues [was
> > svncommit:trunk/buildroot: target/device target/device/Atmel targetetc...]
> >
> >
> >> On Mon, Oct 15, 2007 at 11:25:52PM +0200, Ulf Samuelsson wrote:
> >>>>   That commit introduced gcc 4.2.1 to avr32, which builds ok, but the
> >>>> compiler still has some bugs, specially the C++ compiler and the
> >>>> template engine.
> >>>
> >>>
> >>> I tested with
> >>>
> >>> make atngw100_defconfig
> >>> make
> >>>
> >>> which manages to build both the linux and the root fs.
> >>
> >> It failed for me twice.  First with the libtool error I posted
> >> recently, then in uboot.
> >>
> >> ...
> >> rm -rf
> >> /home/dev/AVR32/Buildroot/buildroot/project_build_avr32/atngw100/buildroot-config
> >> mkdir -p /home/dev/AVR32/Buildroot/buildroot/project_build_avr32/atngw100
> >> cp -dpRf package/config/buildroot-config
> >> /home/dev/AVR32/Buildroot/buildroot/project_build_avr32/atngw100/buildroot-config
> >> cp target/device/Atmel/atngw100/u-boot/atngw100.h
> >> /home/dev/AVR32/Buildroot/buildroot/build_avr32/u-boot-1.2.0-atmel/include/configs/.
> >> cp: cannot stat `target/device/Atmel/atngw100/u-boot/atngw100.h': No such
> >> file or directory
> >> ...
> >>
> >> --
> >> Don
> >
> >
> > Don't know why the libtool stuff fails, but the u-boot was never supported
> > for ngw100.
> > It might be as simple as adding the file:
> >
> > ...
> >
> > Is U-Boot on by default?
> > Maybe I turned it off, before I built it.
> >
> > There is a later u-boot at the u-boot home page.
>
> I just did a clean buildroot checkout and then
>
>         make atngw100_defconfig
>         make
>
> If U-Boot shouldn't be build for the atngw100_defconfig then that
> config should turn it off.
>
> --
> Don
>

[Buildroot] AVR32 4.1.2 toolchain build issues [was svncommit:trunk/buildroot: target/device target/device/Atmel targetetc...]

[Hans-Christian Egtvedt]

On Tue, 2007-10-16 at 02:46 +0100, Thiago A. Corr?a wrote:
> Ok.... got it to build... it happens to be that atngw100_defconfig now
> builds to a dir without nofp sufix, which makes me wonder if ppl have
> decided weather this thing has or doesn't has an FP, perhaps it's a
> paradox, or a dogma. You just have to belive it works. *smile*
> 

It does not have an FPU, probably just a bad defconfig.

> Anyway, disabled libdaemon, which I never use anyway, and now I get
> the uboot issue as well.... but at least I can work now. It should be
> easily enough to pull uboot from the Atmel AVR32 fork and figure out
> what's wrong. Dealing with packages is so much easier.
> 

The AVR32 fork has the bootloader in target/bootloader/u-boot, and is
quite different from the one in the Atmel directory.

> Btw, is there a reason why u-boot is buried into Atmel folder?
> Shouldn't other archs/chips use it as well?
> 

The AVR32 fork on atmel.no tries to do the bootloader general for all
archs.

> Hopefully I will come back with patches once more (have a better
> qtopia building, in a single stage, on the works).
> 

You can't, Qtopia hard codes the path to the libraries inside the
libraries. I have tried and ended up having to do a two stage build. One
for staging_dir and one for the target dir.

-- 
With kind regards,
Hans-Christian Egtvedt, Applications Engineer

[Buildroot] AVR32 4.1.2 toolchain build issues[was svncommit:trunk/buildroot: target/devicetarget/device/Atmel targetetc...]

[Ulf Samuelsson]

> On Tue, 2007-10-16 at 02:46 +0100, Thiago A. Corr?a wrote:
>> Ok.... got it to build... it happens to be that atngw100_defconfig now
>> builds to a dir without nofp sufix, which makes me wonder if ppl have
>> decided weather this thing has or doesn't has an FP, perhaps it's a
>> paradox, or a dogma. You just have to belive it works. *smile*
>>
>
> It does not have an FPU, probably just a bad defconfig.
>

Why not add a  "depends on !AVR32" patch to uClibc    KConfig which disables 
the possibility to select the bad FPU option?
If an AVR32 with a FPU appears (wish, wish :-) then this option can be 
removed.

Best Regards
Ulf Samuelsson 

[Buildroot] AVR32 4.1.2 toolchain build issues [was svncommit:trunk/buildroot: target/device target/device/Atmel targetetc...]

[Thiago A. Corrêa]

On 10/16/07, Hans-Christian Egtvedt <hcegtvedt@atmel.com> wrote:
> On Tue, 2007-10-16 at 02:46 +0100, Thiago A. Corr?a wrote:
> > Ok.... got it to build... it happens to be that atngw100_defconfig now
> > builds to a dir without nofp sufix, which makes me wonder if ppl have
> > decided weather this thing has or doesn't has an FP, perhaps it's a
> > paradox, or a dogma. You just have to belive it works. *smile*
> >
>
> It does not have an FPU, probably just a bad defconfig.

That was an attempt to pull up a joke, but looks that it wasn't much successful.

>
> The AVR32 fork has the bootloader in target/bootloader/u-boot, and is
> quite different from the one in the Atmel directory.

Different how? Version? If it is still the Das U-Boot, how different can it be?

> > Btw, is there a reason why u-boot is buried into Atmel folder?
> > Shouldn't other archs/chips use it as well?
> >
>
> The AVR32 fork on atmel.no tries to do the bootloader general for all
> archs.

Yes. I've noticed that :)
But I don't see any merges any time soon.... but when one does happen,
that should mean a little bit less effort.
Btw, still on the subject, how about bringing those snapshots a few
hundred revisions up to date? For instance, all the BR_avr32 checks
are backwards in the 2 trees, generating several stupid and avoidable
diffs.... Again, this is more work when/if a merge occurs. And I hope
it does.

> > Hopefully I will come back with patches once more (have a better
> > qtopia building, in a single stage, on the works).
> >
>
> You can't, Qtopia hard codes the path to the libraries inside the
> libraries. I have tried and ended up having to do a two stage build. One
> for staging_dir and one for the target dir.

Yes, I know. But it's mostly used on qmake to generate the project,
and that you should link against the stuff in the staging_dir. It
should also be used for plugin loading, but that can be overridden in
several ways. I have to check on the docs. At the worst case, it
should still be possible to sed qconfig.cpp (which is where the
hardcoded stuff lies), then rebuild from the already built tree, so
it's only 1 file to compile + link of everything else.

Besides, there is a lot of hardcoded configure options in there that I
don't really like, so, I'm adding config options to those in the
kconfig. For one, forcing on libjpeg isn't very nice :)

Friendly Regards,
   Thiago A. Correa

[Buildroot] AVR32 4.1.2 toolchain build issues [was svncommit:trunk/buildroot: target/device target/device/Atmel targetetc...]

[Hans-Christian Egtvedt]

On Tue, 2007-10-16 at 12:32 +0100, Thiago A. Corr?a wrote:
> On 10/16/07, Hans-Christian Egtvedt <hcegtvedt@atmel.com> wrote:
> > On Tue, 2007-10-16 at 02:46 +0100, Thiago A. Corr?a wrote:
> >
> > The AVR32 fork has the bootloader in target/bootloader/u-boot, and is
> > quite different from the one in the Atmel directory.
> 
> Different how? Version? If it is still the Das U-Boot, how different can it be?
>

It is the latest release + some from upstream GIT and some from Atmel
GIT. Mainly NGW100 support from Atmel GIT.

> > > Btw, is there a reason why u-boot is buried into Atmel folder?
> > > Shouldn't other archs/chips use it as well?
> > >
> >
> > The AVR32 fork on atmel.no tries to do the bootloader general for all
> > archs.
> 
> Yes. I've noticed that :)
> But I don't see any merges any time soon.... but when one does happen,
> that should mean a little bit less effort.

Depends what you mean by soon, it will probably be after the first
stable release with all the features enabled by default working.

> Btw, still on the subject, how about bringing those snapshots a few
> hundred revisions up to date? For instance, all the BR_avr32 checks
> are backwards in the 2 trees, generating several stupid and avoidable
> diffs.... Again, this is more work when/if a merge occurs. And I hope
> it does.
> 

I will sync after the next release, I also plan to get out a GIT
repository for those who want easier access to the Atmel specific fork.

> > > Hopefully I will come back with patches once more (have a better
> > > qtopia building, in a single stage, on the works).
> > >
> >
> > You can't, Qtopia hard codes the path to the libraries inside the
> > libraries. I have tried and ended up having to do a two stage build. One
> > for staging_dir and one for the target dir.
> 
> Yes, I know. But it's mostly used on qmake to generate the project,
> and that you should link against the stuff in the staging_dir. It
> should also be used for plugin loading, but that can be overridden in
> several ways. I have to check on the docs. At the worst case, it
> should still be possible to sed qconfig.cpp (which is where the
> hardcoded stuff lies), then rebuild from the already built tree, so
> it's only 1 file to compile + link of everything else.
> 

It sounds really nice, would reduce the compile time and disk usage a
lot.

> Besides, there is a lot of hardcoded configure options in there that I
> don't really like, so, I'm adding config options to those in the
> kconfig. For one, forcing on libjpeg isn't very nice :)
> 

More config options are welcome (-: When I started on Qtopia, the build
process in Buildroot was not working at all.

-- 
With kind regards,
Hans-Christian Egtvedt, Applications Engineer

[Buildroot] AVR32 4.1.2 toolchain build issues [was svncommit:trunk/buildroot: target/device target/device/Atmel targetetc...]

[Thomas Lundquist]

On Tue, Oct 16, 2007 at 01:46:08PM +0200, Hans-Christian Egtvedt wrote:

> More config options are welcome (-: When I started on Qtopia, the build
> process in Buildroot was not working at all.

Which tells us something about how fast packages 
make files bitrot.

When added, it worked on both arm and i386.

Sorry I haven't had time to maintain it, the customer 
stopped paying me when it worked and I never needed it myself.


Thomas.

[Buildroot] AVR32 4.1.2 toolchain build issues [was svncommit:trunk/buildroot: target/device target/device/Atmel targetetc...]

[Ulf Samuelsson]

> Ok.... got it to build... it happens to be that atngw100_defconfig now
> builds to a dir without nofp sufix, which makes me wonder if ppl have
> decided weather this thing has or doesn't has an FP, perhaps it's a
> paradox, or a dogma. You just have to belive it works. *smile*
>
> Anyway, disabled libdaemon, which I never use anyway, and now I get
> the uboot issue as well.... but at least I can work now. It should be
> easily enough to pull uboot from the Atmel AVR32 fork and figure out
> what's wrong. Dealing with packages is so much easier.
>
> Btw, is there a reason why u-boot is buried into Atmel folder?
> Shouldn't other archs/chips use it as well?
>

It is not the mainstream U-Boot tree.
It is a prepatched U-boot to support the AT91 series and should support the 
AVR32 as well.
The AVR32 Buildroot at www.atmel.no/buildroot is a more up to date version 
though,



Best Regards
Ulf Samuelsson                ulf at atmel.com
Atmel Nordic AB
Mail:  Box 2033, 174 02 Sundbyberg, Sweden
Visit:  Kavalleriv?gen 24, 174 58 Sundbyberg, Sweden
Phone +46 (8) 441 54 22     Fax +46 (8) 441 54 29
GSM    +46 (706) 22 44 57

Technical support when I am not available:
AT89 C51 Applications Group: mailto:micro.hotline at nto.atmel.com
AT90 AVR Applications Group: mailto:avr at atmel.com
AT91 ARM Applications Group: mailto:at91support at atmel.com
FPSLIC Application Group: mailto:fpslic at atmel.com Best AVR
link: www.avrfreaks.net 

[Buildroot] AVR32 4.1.2 toolchain build issues [wassvncommit:trunk/buildroot: target/device target/device/Atmeltargetetc...]

[Ulf Samuelsson]

link: www.avrfreaks.net
----- Original Message ----- 
From: "don" <don_reid@comcast.net>
To: "Ulf Samuelsson" <ulf@atmel.com>
Cc: "Thiago A. Corr?a" <thiago.correa@gmail.com>; <buildroot@uclibc.org>
Sent: Tuesday, October 16, 2007 1:49 AM
Subject: Re: [Buildroot] AVR32 4.1.2 toolchain build issues 
[wassvncommit:trunk/buildroot: target/device 
target/device/Atmeltargetetc...]


> On Tue, Oct 16, 2007 at 12:22:03AM +0200, Ulf Samuelsson wrote:
>> link: www.avrfreaks.net
>> ----- Original Message ----- From: "don" <don_reid@comcast.net>
>> To: "Ulf Samuelsson" <ulf@atmel.com>
>> Cc: "Thiago A. Corr?a" <thiago.correa@gmail.com>; <buildroot@uclibc.org>
>> Sent: Tuesday, October 16, 2007 12:17 AM
>> Subject: Re: [Buildroot] AVR32 4.1.2 toolchain build issues [was
>> svncommit:trunk/buildroot: target/device target/device/Atmel 
>> targetetc...]
>>
>>
>>> On Mon, Oct 15, 2007 at 11:25:52PM +0200, Ulf Samuelsson wrote:
>>>>>   That commit introduced gcc 4.2.1 to avr32, which builds ok, but the
>>>>> compiler still has some bugs, specially the C++ compiler and the
>>>>> template engine.
>>>>
>>>>
>>>> I tested with
>>>>
>>>> make atngw100_defconfig
>>>> make
>>>>
>>>> which manages to build both the linux and the root fs.
>>>
>>> It failed for me twice.  First with the libtool error I posted
>>> recently, then in uboot.
>>>
>>> ...
>>> rm -rf
>>> /home/dev/AVR32/Buildroot/buildroot/project_build_avr32/atngw100/buildroot-config
>>> mkdir -p 
>>> /home/dev/AVR32/Buildroot/buildroot/project_build_avr32/atngw100
>>> cp -dpRf package/config/buildroot-config
>>> /home/dev/AVR32/Buildroot/buildroot/project_build_avr32/atngw100/buildroot-config
>>> cp target/device/Atmel/atngw100/u-boot/atngw100.h
>>> /home/dev/AVR32/Buildroot/buildroot/build_avr32/u-boot-1.2.0-atmel/include/configs/.
>>> cp: cannot stat `target/device/Atmel/atngw100/u-boot/atngw100.h': No 
>>> such
>>> file or directory
>>> ...
>>>
>>> -- 
>>> Don
>>
>>
>> Don't know why the libtool stuff fails, but the u-boot was never 
>> supported
>> for ngw100.
>> It might be as simple as adding the file:
>>
>> ...
>>
>> Is U-Boot on by default?
>> Maybe I turned it off, before I built it.
>>
>> There is a later u-boot at the u-boot home page.
>
> I just did a clean buildroot checkout and then
>
> make atngw100_defconfig
> make
>
> If U-Boot shouldn't be build for the atngw100_defconfig then that
> config should turn it off.
>


It is not, that it should not build, it is a small matter of adding that 
file,
I have not been aware of that problem for long.
The NGW100 support was added and then soon afterwards,
the AVR32 toolchain was broken.
The default configuration did not include U-boot at that time.

Best Regards
Ulf Samuelsson                ulf at atmel.com
Atmel Nordic AB
Mail:  Box 2033, 174 02 Sundbyberg, Sweden
Visit:  Kavalleriv?gen 24, 174 58 Sundbyberg, Sweden
Phone +46 (8) 441 54 22     Fax +46 (8) 441 54 29
GSM    +46 (706) 22 44 57