All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Steeve <joe@sliceware.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Compilation failure (gcc options..)
Date: Mon, 13 Nov 2006 13:49:50 +0530	[thread overview]
Message-ID: <45582AA6.7040401@sliceware.com> (raw)
In-Reply-To: <03C644EDACDDFE44A97012968D879944123C243A@ot-mail01.de.bosch.com>

Jonas Mark (ST-FIR/ENG1) wrote:
> Googling for this gives you for example this very helpful link: 
> http://gcc.gnu.org/onlinedocs/gcc-4.1.1/gcc/Preprocessor-Options.html#Pr
>  eprocessor-Options

Thanks., I figured that :)

> Hint on googling: When looking for keywords that start with a dash
> put them in quotes or else Google will only return pages that do
> *not* contain these keywords. Additionally, limiting Google to a
> specific site helps as well. So your Google search could have been
> 
> gcc "-mq" site:gcc.gnu.org

Thanks again., I knew that the '-' was screwing it up., but did not know
quoting it would help. :)

> So most likely your GCC tool chain is broken or too old. I am not an
> ARM expert but the ELDK 4.0 from Denx 
> (http://www.denx.de/en/News/PressReleaseELDK40) is most likely a good
>  choice.

Yeah., the version of gcc i use is 2.95.3. It does not have the -MT/-MQ
options in it. I'll try the ELDK compilers :)

-- 
Joe Steeve
Sliceware Private Limited

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
Url : http://lists.denx.de/pipermail/u-boot/attachments/20061113/c175f434/attachment.pgp 

  reply	other threads:[~2006-11-13  8:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-13  8:00 [U-Boot-Users] Compilation failure (gcc options..) Jonas Mark
2006-11-13  8:19 ` Joe Steeve [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-13  6:48 Joe Steeve

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=45582AA6.7040401@sliceware.com \
    --to=joe@sliceware.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 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.