From: Pierre Aubert <p.aubert@staubli.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] U-Boot v2015.01-rc2 released
Date: Mon, 1 Dec 2014 02:20:21 -0700 (MST) [thread overview]
Message-ID: <1417425621477-197861.post@n7.nabble.com> (raw)
In-Reply-To: <54746543.10006@free.fr>
Hello Guillaume,
Guillaume Gardet wrote
> Le 25/11/2014 11:19, Lukasz Majewski a ?crit :
>> Hi Guillaume,
>>
>>> Le 24/11/2014 23:13, Tom Rini a ?crit :
>>>> Hey all,
>>>>
>>>> I've pushed v2015.01-rc2 out to the repository and tarballs should
>>>> exist soon.
>>>>
>>>> I'm tagging later in the day than I wanted to, but that's OK.
>>>>
>>>> There's a fair number of things that've gone in since -rc1, but I
>>>> think that's OK. And there's a few things that still need to go in.
>>>>
>>>> For example, I just pushed the changes to allow bigger files to be
>>>> read but that's broken MIPS+private libgcc and ARM+hf toolchain and
>>>> others too. I posted a patch for this and tested it locally with a
>>>> 32MB file but I'd like others to review too (Thanks Simon!) before
>>>> pushing it in.
>>>>
>>>> As always, if anything else is broken please speak up.
>>>
>>> I guess this the ARM+hf problem you mentioned:
>>> ********************************************************************************
>>> LD u-boot
>>> ld.bfd:
>>> error: /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8/libgcc.a(bpabi.o)
>>> uses VFP register arguments, u-boot does not ld.bfd: failed to merge
>>> target specific data of
>>> file /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8/libgcc.a(bpabi.o)
>>> ld.bfd:
>>> error: /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8/libgcc.a(_divdi3.o)
>>> uses VFP register arguments, u-boot does not ld.bfd: failed to merge
>>> target specific data of
>>> file /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8/libgcc.a(_divdi3.o)
>>> ld.bfd:
>>> error: /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8/libgcc.a(_udivdi3.o)
>>> uses VFP register arguments, u-boot does not ld.bfd: failed to merge
>>> target specific data of
>>> file /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8/libgcc.a(_udivdi3.o)
>>> ********************************************************************************
>>>
>> I experience the same issue:
>>
>> Working toolchain:
>> /opt/eldk-5.4/armv7a/sysroots/i686-eldk-linux/usr/bin/armv7a-vfp-neon-linux-gnueabi/arm-linux-gnueabi-
>>
>> Toolchain with errors:
>> /home/DIGITAL/l.majewski/gcc-linaro-arm-linux-gnueabihf-4.8-2013.12_linux/bin/arm-linux-gnueabihf-
>>
>> Building smdk2410 board...
>> /home/DIGITAL/l.majewski/gcc-linaro-arm-linux-gnueabihf-4.8-2013.12_linux/bin/arm-linux-gnueabihf-ld.bfd:
>> error:
>> /home/DIGITAL/l.majewski/gcc-linaro-arm-linux-gnueabihf-4.8-2013.12_linux/bin/../lib/gcc/arm-linux-gnueabihf/4.8.3/libgcc.a(bpabi.o)
>> uses VFP register arguments, u-boot does
>> not
>> /home/DIGITAL/l.majewski/gcc-linaro-arm-linux-gnueabihf-4.8-2013.12_linux/bin/arm-linux-gnueabihf-ld.bfd:
>> error:
>> /home/DIGITAL/l.majewski/gcc-linaro-arm-linux-gnueabihf-4.8-2013.12_linux/bin/../lib/gcc/arm-linux-gnueabihf/4.8.3/libgcc.a(_divdi3.o)
>> uses VFP register arguments, u-boot does
>> not
>> /home/DIGITAL/l.majewski/gcc-linaro-arm-linux-gnueabihf-4.8-2013.12_linux/bin/arm-linux-gnueabihf-ld.bfd:
>> error:
>> /home/DIGITAL/l.majewski/gcc-linaro-arm-linux-gnueabihf-4.8-2013.12_linux/bin/../lib/gcc/arm-linux-gnueabihf/4.8.3/libgcc.a(_udivdi3.o)
>> uses VFP register arguments, u-boot does not make: *** [u-boot] Error 1
>>
>>
>>
>>> Is there any pending patch to fix this one?
>> +1
>
>
> I got it compiling by removing -msoft-float flag:
> ********************************************************************************
> diff --git a/arch/arm/config.mk b/arch/arm/config.mk
> index c339e6d..cd41e48 100644
> --- a/arch/arm/config.mk
> +++ b/arch/arm/config.mk
> @@ -16,7 +16,7 @@ endif
> LDFLAGS_FINAL += --gc-sections
> PLATFORM_RELFLAGS += -ffunction-sections -fdata-sections \
> -fno-common -ffixed-r9
> -PLATFORM_RELFLAGS += $(call cc-option, -msoft-float) \
> +PLATFORM_RELFLAGS += \
> $(call cc-option,-mshort-load-bytes,$(call
> cc-option,-malignment-traps,))
>
> # Support generic board on ARM
>
> ********************************************************************************
>
> Is it an acceptable patch? If so, I can send it as a real patch.
>
>
> Guillaume
I experimented the same issue while building u-boot for the mx6dlsabresd
platform.
Your patch doesn't solve the issue. The boot is compiling and linking but
raise some hardware exception at runtime while loading files from fat
filesystems.
The patch http://patchwork.ozlabs.org/patch/415336/ solves the issue for the
iMX6.
Regards
Pierre Aubert
--
View this message in context: http://u-boot.10912.n7.nabble.com/ANN-U-Boot-v2015-01-rc2-released-tp197341p197861.html
Sent from the U-Boot mailing list archive at Nabble.com.
next prev parent reply other threads:[~2014-12-01 9:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 22:13 [U-Boot] [ANN] U-Boot v2015.01-rc2 released Tom Rini
2014-11-25 8:51 ` Hans de Goede
2014-11-26 16:24 ` Tom Rini
2014-11-25 8:57 ` Wolfgang Denk
2014-11-25 10:06 ` Guillaume Gardet
2014-11-25 10:19 ` Lukasz Majewski
2014-11-25 11:17 ` Guillaume Gardet
2014-12-01 9:20 ` Pierre Aubert [this message]
2014-11-25 12:30 ` Tom Rini
2014-11-25 12:58 ` Guillaume Gardet
2014-11-25 14:37 ` Guillaume Gardet
-- strict thread matches above, loose matches on Subject: below --
2015-02-17 20:25 Tom Rini
2015-02-17 20:40 ` Simon Glass
2015-02-18 5:34 ` Sinan Akman
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=1417425621477-197861.post@n7.nabble.com \
--to=p.aubert@staubli.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