public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] About the compile problem for eldk4.1+u-boot.1.3.1
Date: Thu, 27 Dec 2007 02:47:35 +0100	[thread overview]
Message-ID: <20071227014735.91CC02488A@gemini.denx.de> (raw)
In-Reply-To: Your message of "Thu, 27 Dec 2007 09:16:53 +0800." <1392658266.70941198718213247.JavaMail.coremail@bj163app103.163.com>

In message <1392658266.70941198718213247.JavaMail.coremail@bj163app103.163.com> you wrote:
>
> What has the subject line to do with the content of this message?
> Please make sure to read http://www.catb.org/%7eesr/faqs/smart-questions.html
> >> I can't open this link.

Why not? You may have to install a web browser, of course...

> Works fine for me (on a Fedora 7 system)...
> >>Is it relevant to the linux system, I am now use the ubuntu7.10.

It should work on Ubuntu, too.

> Either your source tree has been modified / corrupted, or your "Make"
> tool is somehow broken - or you did not literally copy the build log.
> 
> >> Maybe it is due to the IE decode issue, in fact they are:

What is the "IE decode issue" ?? Please make sure to use a clean,
unmodified source tree.

> /bmp_logo logos/denx.bmp >/arm44b0/u-boot-1.3.1/include/bmp_logo.h
> /bmp_logo: 1: Syntax error: word unexpected (expecting ")")
>  
> I am curious to see it use 'GCC' to compile my 'tools' in the first time, while use my cross compiler 'arm-linux-gcc' to compile 'tools' in the second time, even if I set the the 'GCC' to a symbol link to my cross compiler, the problem still exists.

Don't mess around with your tools like that.

> And STOP posting HTML here!
> >> I tried many ways to kill these HTML, but seems take no effect, now I changed the decode in my IE, hopeful this will work.

No, it did not work.

> ------=_Part_19157_587839438.1198718213246
> Content-Type: text/html; charset=gbk
> Content-Transfer-Encoding: quoted-printable

Please STOP this!

See http://expita.com/nomime.html for detailed instructions.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Es ist nicht genug zu wissen, man mu? auch anwenden; es ist nicht ge-
nug zu wollen, man mu? auch tun.   -- Goethe, Maximen und Reflexionen

  reply	other threads:[~2007-12-27  1:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-17 23:52 [U-Boot-Users] Linux kernel hang (infinite loop) Madhu Saravana Sibi Govindan
2006-07-18  6:27 ` Stefan Roese
2006-07-18  6:40 ` Wolfgang Denk
2007-12-26  2:38   ` jxnuxdy
2007-12-26  2:40     ` [U-Boot-Users] Can't compile u-boot-1.3.1 in the first time jxnuxdy
2007-12-26  9:05     ` [U-Boot-Users] Linux kernel hang (infinite loop) Wolfgang Denk
2007-12-27  1:16       ` [U-Boot-Users] About the compile problem for eldk4.1+u-boot.1.3.1 jxnuxdy
2007-12-27  1:47         ` Wolfgang Denk [this message]
2007-12-29  2:43           ` jxnuxdy
2007-12-29 14:21             ` Wolfgang Denk
2008-01-02  4:54               ` [U-Boot-Users] how to convert u-boot to s19 file format jxnuxdy
2008-01-02  8:55                 ` Wolfgang Denk

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=20071227014735.91CC02488A@gemini.denx.de \
    --to=wd@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