From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: add _lshrdi3.S
Date: Thu, 23 Jul 2009 14:16:49 +0200 [thread overview]
Message-ID: <4A6854B1.5000205@denx.de> (raw)
In-Reply-To: <20090723114131.6061D832E416@gemini.denx.de>
Hello Wolfgang,
Wolfgang Denk wrote:
> In message <4A684908.8070402@invitel.hu> you wrote:
>> Signed-off-by: Heiko Schocher <hs@denx.de>
>> ---
>> lib_arm/Makefile | 1 +
>> lib_arm/_lshrdi3.S | 46 ++++++++++++++++++++++++++++++++++++++++++++++
>> 2 files changed, 47 insertions(+), 0 deletions(-)
>> create mode 100644 lib_arm/_lshrdi3.S
>
> Why should we add this? Where it is needed?
This is needed for the upcoming suen3 support.
Maybe I sould have written this in the commit
message?
This board uses NAND, and if I compile it, I get this
errors:
[hs at pollux u-boot]$ make mrproper
[hs at pollux u-boot]$ make suen3_config
Configuring for suen3 board...
[hs at pollux u-boot]$ make USE_PRIVATE_LIBGCC=yes -s all
drivers/mtd/nand/libnand.a(nand_base.o): In function `nand_do_write_oob':
/home/hs/keymile/suen3/u-boot/drivers/mtd/nand/nand_base.c:2019: undefined reference to `__lshrdi3'
drivers/mtd/nand/libnand.a(nand_base.o): In function `nand_erase_nand':
/home/hs/keymile/suen3/u-boot/drivers/mtd/nand/nand_base.c:2199: undefined reference to `__lshrdi3'
/home/hs/keymile/suen3/u-boot/drivers/mtd/nand/nand_base.c:2198: undefined reference to `__lshrdi3'
drivers/mtd/nand/libnand.a(nand_base.o): In function `nand_do_read_oob':
/home/hs/keymile/suen3/u-boot/drivers/mtd/nand/nand_base.c:1519: undefined reference to `__lshrdi3'
drivers/mtd/nand/libnand.a(nand_bbt.o): In function `search_bbt':
/home/hs/keymile/suen3/u-boot/drivers/mtd/nand/nand_bbt.c:482: undefined reference to `__lshrdi3'
drivers/mtd/nand/libnand.a(nand_bbt.o):/home/hs/keymile/suen3/u-boot/drivers/mtd/nand/nand_bbt.c:413: more undefined references to `__lshrdi3' follow
make: *** [u-boot] Fehler 1
[hs at pollux u-boot]$
above patch fixes this. And I thought better to post such
a fix immediately ...
bye
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2009-07-23 12:16 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 19:36 [U-Boot] [PATCH v3] libgcc inclusion from common Makefile overwritable from platform configs files Jean-Christophe PLAGNIOL-VILLARD
2009-07-08 19:42 ` Scott Wood
2009-07-08 20:09 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-08 20:14 ` [U-Boot] [PATCH V4] " Jean-Christophe PLAGNIOL-VILLARD
2009-07-08 20:26 ` Scott Wood
2009-07-08 20:33 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-08 20:38 ` [U-Boot] [PATCH V5] " Jean-Christophe PLAGNIOL-VILLARD
2009-07-08 20:38 ` [U-Boot] [PATCH 2/2] netstar/voiceblue: remove no-need libgcc link for eeprom standalone Jean-Christophe PLAGNIOL-VILLARD
2009-07-20 22:03 ` Wolfgang Denk
2009-07-08 20:55 ` [U-Boot] [PATCH V5] libgcc inclusion from common Makefile overwritable from platform configs files Wolfgang Denk
2009-07-08 21:19 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-08 21:29 ` Wolfgang Denk
2009-07-08 20:30 ` [U-Boot] [PATCH V4] " Wolfgang Denk
2009-07-08 20:45 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-08 20:47 ` Mike Frysinger
2009-07-09 10:24 ` [U-Boot] [PATCH 1/2 v6] Make libgcc inclusion from common Makefile overridable by platform config file Jean-Christophe PLAGNIOL-VILLARD
2009-07-12 7:54 ` Dirk Behme
2009-07-12 8:02 ` Stefan Roese
2009-07-12 8:15 ` Dirk Behme
2009-07-12 10:29 ` Wolfgang Denk
2009-07-12 12:06 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-12 12:13 ` Dirk Behme
2009-07-12 12:39 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-12 14:36 ` Wolfgang Denk
2009-07-12 14:55 ` Dirk Behme
2009-07-12 15:50 ` Wolfgang Denk
2009-07-12 16:12 ` Dirk Behme
2009-07-12 18:17 ` Wolfgang Denk
2009-07-12 19:22 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-12 19:35 ` Wolfgang Denk
2009-07-12 19:51 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-12 21:27 ` Wolfgang Denk
2009-07-12 16:17 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-12 18:29 ` Wolfgang Denk
2009-07-12 19:06 ` Dirk Behme
2009-07-12 19:30 ` Wolfgang Denk
2009-07-13 9:25 ` Mike Frysinger
2009-07-13 16:00 ` Dirk Behme
2009-07-15 22:18 ` Scott Wood
2009-07-15 22:43 ` Mike Frysinger
2009-07-15 23:03 ` Scott Wood
2009-07-15 23:54 ` Mike Frysinger
2009-07-16 15:36 ` Scott Wood
2009-07-16 15:42 ` Wolfgang Denk
2009-07-16 15:56 ` Scott Wood
2009-07-17 11:27 ` Detlev Zundel
2009-07-17 11:37 ` Wolfgang Denk
2009-07-17 11:41 ` Wolfgang Denk
2009-07-17 15:24 ` Scott Wood
2009-07-16 11:11 ` Wolfgang Denk
2009-07-13 7:36 ` Stefan Roese
2009-07-13 15:46 ` Dirk Behme
2009-07-13 18:16 ` Mike Frysinger
2009-07-23 9:36 ` Wolfgang Denk
2009-07-23 11:09 ` [U-Boot] [PATCH] Make linking against libgcc configurable Wolfgang Denk
2009-07-23 11:15 ` [U-Boot] [PATCH v2] " Wolfgang Denk
2009-07-23 11:27 ` [U-Boot] [PATCH] arm: add _lshrdi3.S Heiko Schocher
2009-07-23 11:41 ` Wolfgang Denk
2009-07-23 12:16 ` Heiko Schocher [this message]
2009-07-26 22:11 ` Wolfgang Denk
2009-07-23 13:28 ` [U-Boot] [PATCH v2] Make linking against libgcc configurable Daniel Gorsulowski
2009-07-23 14:12 ` Heiko Schocher
2009-07-23 14:43 ` Daniel Gorsulowski
2009-07-23 14:48 ` Daniel Gorsulowski
2009-07-23 15:33 ` Heiko Schocher
2009-07-24 6:07 ` Daniel Gorsulowski
2009-07-27 6:26 ` Heiko Schocher
2009-07-23 16:45 ` Wolfgang Denk
2009-07-26 22:11 ` 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=4A6854B1.5000205@denx.de \
--to=hs@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