From: Jan Kiszka <jan.kiszka@siemens.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v8, 2/6] fat: Prepare API change for files greater than 2GB
Date: Thu, 27 Nov 2014 09:06:49 +0100 [thread overview]
Message-ID: <5476DB99.7070300@siemens.com> (raw)
In-Reply-To: <20141124221239.GM21184@bill-the-cat>
On 2014-11-24 23:12, Tom Rini wrote:
> On Mon, Nov 17, 2014 at 02:39:35PM -0800, Suriyan Ramasami wrote:
>
>> Change the internal FAT functions to use loff_t for offsets.
>>
>> Signed-off-by: Suriyan Ramasami <suriyan.r@gmail.com>
>>
>> Acked-by: Simon Glass <sjg@chromium.org>
>
> Applied to u-boot/master, thanks!
Since this commit, I'm getting
...
LD lib/built-in.o
LD u-boot
arm-linux-gnueabihf-ld.bfd: error:
/opt/gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/bin/../lib/gcc/arm-linux-gnueabihf/4.9.2/libgcc.a(bpabi.o)
uses VFP register arguments, u-boot does not
arm-linux-gnueabihf-ld.bfd: failed to merge target specific data of file
/opt/gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/bin/../lib/gcc/arm-linux-gnueabihf/4.9.2/libgcc.a(bpabi.o)
arm-linux-gnueabihf-ld.bfd: error:
/opt/gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/bin/../lib/gcc/arm-linux-gnueabihf/4.9.2/libgcc.a(_divdi3.o)
uses VFP register arguments, u-boot does not
arm-linux-gnueabihf-ld.bfd: failed to merge target specific data of file
/opt/gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/bin/../lib/gcc/arm-linux-gnueabihf/4.9.2/libgcc.a(_divdi3.o)
arm-linux-gnueabihf-ld.bfd: error:
/opt/gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/bin/../lib/gcc/arm-linux-gnueabihf/4.9.2/libgcc.a(_udivdi3.o)
uses VFP register arguments, u-boot does not
arm-linux-gnueabihf-ld.bfd: failed to merge target specific data of file
/opt/gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/bin/../lib/gcc/arm-linux-gnueabihf/4.9.2/libgcc.a(_udivdi3.o)
Any idea what goes wrong?
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2014-11-27 8:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 22:39 [U-Boot] [PATCH v8 0/6] fs: fat/ext4/sandbox - Deal with files greater than 2GB Suriyan Ramasami
2014-11-17 22:39 ` [U-Boot] [PATCH v8 1/6] sandbox: Use md5sum and fatwrite to enable testing of fs commands Suriyan Ramasami
2014-11-24 22:12 ` [U-Boot] [U-Boot, v8, " Tom Rini
2014-11-17 22:39 ` [U-Boot] [PATCH v8 2/6] fat: Prepare API change for files greater than 2GB Suriyan Ramasami
2014-11-24 22:12 ` [U-Boot] [U-Boot, v8, " Tom Rini
2014-11-27 8:06 ` Jan Kiszka [this message]
2014-11-27 12:11 ` Tom Rini
2014-11-27 12:23 ` Jan Kiszka
2014-11-17 22:39 ` [U-Boot] [PATCH v8 3/6] ext4: " Suriyan Ramasami
2014-11-24 22:12 ` [U-Boot] [U-Boot, v8, " Tom Rini
2014-11-17 22:39 ` [U-Boot] [PATCH v8 4/6] sandbox: " Suriyan Ramasami
2014-11-24 22:12 ` [U-Boot] [U-Boot, v8, " Tom Rini
2014-11-17 22:39 ` [U-Boot] [PATCH v8 5/6] fs: API changes enabling extra parameter to return size of type loff_t Suriyan Ramasami
2014-11-24 22:12 ` [U-Boot] [U-Boot, v8, " Tom Rini
2014-11-17 22:39 ` [U-Boot] [PATCH v8 6/6] sandbox: script for testing sandbox/ext4/fat/fs commands Suriyan Ramasami
2014-11-24 22:13 ` [U-Boot] [U-Boot, v8, " Tom Rini
2014-11-18 8:19 ` [U-Boot] [PATCH v8 0/6] fs: fat/ext4/sandbox - Deal with files greater than 2GB Pavel Machek
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=5476DB99.7070300@siemens.com \
--to=jan.kiszka@siemens.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