From: Devraj Mukherjee <lugs@eternitytechnologies.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] U-boot compile issue with GCC 3.4
Date: Mon, 18 Oct 2004 11:40:58 +1000 [thread overview]
Message-ID: <41731F2A.1020002@eternitytechnologies.com> (raw)
We are users of a Logic PD LH7A400 board. Currently using a Debian host
we managed to make ourselves a GCC for arm (Version 3.4). Now when we
compile U-Boot 1.1.1 patched for LH7A400 we get the following errors.
If anyone can throw some light on them, we would appreciate that.
cc1: error: invalid option `short-load-bytes'
cc1: error: invalid option `short-load-bytes'
make[1]: *** [.depend] Error 1
make[1]: Leaving directory `/home/devraj
Dump from GCC 3.4 for arm --version
devraj at raphaelle:~/lpd7a400/uboot/u-boot-1.1.1$ arm-linux-gcc --version
arm-linux-gcc (GCC) 3.4.1 (Debian 3.4.1-1)
Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Thanks in advance.
Devraj
next reply other threads:[~2004-10-18 1:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 1:40 Devraj Mukherjee [this message]
2004-10-18 4:51 ` [U-Boot-Users] U-boot compile issue with GCC 3.4 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=41731F2A.1020002@eternitytechnologies.com \
--to=lugs@eternitytechnologies.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