public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Shawn Jin <shawnxjin@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: Re: [uClinux-dev] uboot compilation error when using the toolchain arm-elf-tools from uClinux.org
Date: Mon, 9 Aug 2004 18:41:05 -0700	[thread overview]
Message-ID: <c3d0340b040809184118fe47cf@mail.gmail.com> (raw)
In-Reply-To: <20040810001400.GA11472@beast>

Dear David,

> > The code is extracted from the header file processor.h.
> >
> > 51> union debug_insn {
> > 52>      u32     arm;
> > 53>      u16     thumb;
> > 54> };
> > 55>
> > 56> struct debug_entry {
> > 57>        u32                     address;
> > 58>        union debug_insn        insn;
> > 59> };
> >
> > However I really don't think there is any syntax error. It might be a
> > toolchain problem?
> 
> I think,  at least for that version of the toolchain,  it implicitly
> defines "arm",  and I suspect it defines it to be "1",  thus the errors
> you are seeing.  You may be able to add a -Uarm to eth build line,

It did solve the problem. Thank you!

Would you please explain a little bit more why the toolchain
implicitly defines "arm"? Should or should not for a toolchain to
define this? Or we can simply re-name "arm" in struct debug_insn to
another name?

-- 
Best regards,
-Shawn Jin

  reply	other threads:[~2004-08-10  1:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-10  0:01 [U-Boot-Users] uboot compilation error when using the toolchain arm-elf-tools from uClinux.org Shawn Jin
2004-08-10  0:14 ` [U-Boot-Users] Re: [uClinux-dev] " David McCullough
2004-08-10  1:41   ` Shawn Jin [this message]
2004-08-10  3:22     ` [U-Boot-Users] " David McCullough
2004-08-10  6:43 ` [U-Boot-Users] " 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=c3d0340b040809184118fe47cf@mail.gmail.com \
    --to=shawnxjin@gmail.com \
    --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