From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] AVR32 4.1.2 toolchain build issues [was svncommit:trunk/buildroot: target/device target/device/Atmel targetetc...]
Date: Tue, 16 Oct 2007 00:22:03 +0200 [thread overview]
Message-ID: <059501c80f79$dd1305d0$01c4af0a@Glamdring> (raw)
In-Reply-To: 20071015221718.GA15524@reid1.localdomain
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
next prev parent reply other threads:[~2007-10-15 22:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 14:20 [Buildroot] AVR32 4.1.2 toolchain build issues [was svn commit: trunk/buildroot: target/device target/device/Atmel target etc...] Thiago A. Corrêa
2007-10-15 21:25 ` [Buildroot] AVR32 4.1.2 toolchain build issues [was svn commit:trunk/buildroot: " Ulf Samuelsson
2007-10-15 22:17 ` don
2007-10-15 22:22 ` Ulf Samuelsson [this message]
2007-10-15 23:49 ` [Buildroot] AVR32 4.1.2 toolchain build issues [was svncommit:trunk/buildroot: target/device target/device/Atmel targetetc...] don
2007-10-16 1:46 ` Thiago A. Corrêa
2007-10-16 5:15 ` Hans-Christian Egtvedt
2007-10-16 5:57 ` [Buildroot] AVR32 4.1.2 toolchain build issues[was svncommit:trunk/buildroot: target/devicetarget/device/Atmel targetetc...] Ulf Samuelsson
2007-10-16 11:32 ` [Buildroot] AVR32 4.1.2 toolchain build issues [was svncommit:trunk/buildroot: target/device target/device/Atmel targetetc...] Thiago A. Corrêa
2007-10-16 11:46 ` Hans-Christian Egtvedt
2007-10-16 13:10 ` Thomas Lundquist
2007-10-16 5:36 ` Ulf Samuelsson
2007-10-16 5:27 ` [Buildroot] AVR32 4.1.2 toolchain build issues [wassvncommit:trunk/buildroot: target/device target/device/Atmeltargetetc...] Ulf Samuelsson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='059501c80f79$dd1305d0$01c4af0a@Glamdring' \
--to=ulf@atmel.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox