All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] make atngw100_defconfig - errors
Date: Sun, 21 Oct 2007 10:56:33 +0200	[thread overview]
Message-ID: <00a001c813c0$e79e50e0$01c4af0a@Glamdring> (raw)
In-Reply-To: 471A938B.2020004@promwad.com

> Hi Ulf,
>
> I'm trying to do
>
> make atngw100_defconfig
>
> make
>
> and have the following error:
> bzcat /sources/u-boot-1.2.0-atmel-patch.tar.bz2 | tar -C 
> /opt/buildroot/project_build_avr32/atngw100/u-boot-patches -xvf -
> u-boot-1.2.0-atmel-patch/README.txt
> u-boot-1.2.0-atmel-patch/README.txt~
> touch /opt/buildroot/project_build_avr32/atngw100/u-boot-patches/.unpacked
> toolchain/patch-kernel.sh /opt/buildroot/build_avr32/u-boot-1.2.0-atmel 
> /opt/buildroot/project_build_avr32/atngw100/u-boot-patches \*.patch
> touch 
> /opt/buildroot/build_avr32/u-boot-1.2.0-atmel/.patched.u-boot-1.2.0-atmel-patch.tar.bz2
> cp target/device/Atmel/atngw100/u-boot/atngw100.h 
> /opt/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
> make: *** 
> [/opt/buildroot/project_build_avr32/atngw100/u-boot-1.2.0-atmel/.configured] 
> Error 1
>
> Any advice?
>

Download mainstream U-Boot and copy the
"includes/configs/atngw100.h" file to 
"target/device/Atmel/atngw100/u-boot/atngw100.h"
I have seen this before, but did not have time to fix it.


> Toolchain seems built OK except 
> build_avr32/staging_dir/bin/avr32-linux-uclibc-cc is symlink to gcc
> (which is not present in build_avr32/staging_dir/bin/) - seems it should 
> be symlink to avr32-linux-uclibc-gcc
>

Best Regards
Ulf Samuelsson

      reply	other threads:[~2007-10-21  8:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-20 23:47 [Buildroot] make atngw100_defconfig - errors Ivan Kuten
2007-10-21  8:56 ` Ulf Samuelsson [this message]

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='00a001c813c0$e79e50e0$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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.