All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ossy <ossy1980@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] u-boot failed for arm926t using the rc1 plus patches until May 8th
Date: Sun, 09 May 2010 22:18:39 +0200	[thread overview]
Message-ID: <4BE7189F.9000500@gmx.net> (raw)

Dear buildroot mailinglist,

I tried to use th U-Boot integration of buildroot, but it failed with 
the following out put: "...no rule to make target integrator926_config. 
Stop..."

...
--sysroot=/home/ossy/buildroot/buildroot-dev/output/staging/"	\
		 \
		/usr/bin/make -j1 -C 
/home/ossy/buildroot/buildroot-dev/output/build/u-boot-2010.03	\
		integrator926_config
make[1]: Entering directory 
`/home/ossy/buildroot/buildroot-dev/output/build/u-boot-2010.03'
make[1]: *** Keine Regel, um ??integrator926_config?? zu erstellen. 
Schluss.
make[1]: Leaving directory 
`/home/ossy/buildroot/buildroot-dev/output/build/u-boot-2010.03'
make: *** 
[/home/ossy/buildroot/buildroot-dev/output/build/u-boot-2010.03/.configured] 
Fehler 2
...

Please find attached my configuration.
I am using an amd64 host with lenny to compile for target arm.

I skipped the compilation of u-boot and used an external one.

Kind regards,
Marcus
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: uboot-failed.txt
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100509/2de7dc8e/attachment-0001.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: buildroot.config
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100509/2de7dc8e/attachment-0001.diff>

                 reply	other threads:[~2010-05-09 20:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4BE7189F.9000500@gmx.net \
    --to=ossy1980@gmx.net \
    --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.