From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Help!
Date: Mon, 12 Nov 2007 18:50:49 +0100 [thread overview]
Message-ID: <m2sl3bwdxi.fsf@ohwell.denx.de> (raw)
In-Reply-To: <tencent_016C14C45A36606266B00738@qq.com> (gbk's message of "Sun\, 11 Nov 2007 16\:29\:47 +0800")
Hi,
> I had ask for help yesterday,your opinion is helpfull.
> But I had another problem:
> When "make"
> It said:
>
> .................
> .................
> gcc -Wall -pedantic -idirafter ../include -DTEXT_BASE=0x33F80000 -DUSE_HOSTCC
> -O -c -o bmp_logo.o bmp_logo.c
> gcc -Wall -pedantic -idirafter ../include -DTEXT_BASE=0x33F80000 -DUSE_HOSTCC
> -O
> -o bmp_logo bmp_logo.o
> strip bmp_logo
> ./bmp_logo logos/denx.bmp >/home/u-boot-1.1.3/include/bmp_logo.h
> /bin/sh: line 1: ./bmp_logo: cannot execute binary file
> make[1]: *** [/home/u-boot-1.1.3/include/bmp_logo.h] Error 126
> make[1]: Leaving directory `/home/u-boot-1.1.3/tools'
> make: *** [tools] Error 2
>
> Why?Can you tell me ?
The "gcc" that is called from the Makefile obviously cannot compile
programs for your platform (this must *not* be a cross-compiler).
Find out why this is the case - "file bmp_logo" might be helpful here.
Cheers
Detlev
--
Computer scientists do it depth-first.
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
next prev parent reply other threads:[~2007-11-12 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-11 8:29 [U-Boot-Users] Help! clubet
2007-11-12 17:50 ` Detlev Zundel [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-10 2:11 clubet
2007-11-09 12:39 clubet
2007-11-09 13:07 ` Shinya Kuribayashi
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=m2sl3bwdxi.fsf@ohwell.denx.de \
--to=dzu@denx.de \
--cc=u-boot@lists.denx.de \
/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