From: Chris Ruehl <chris.ruehl@gtsys.com.hk>
To: u-boot@lists.denx.de
Subject: [U-Boot] v2013.10 failed build with jffs2 cmd
Date: Wed, 23 Oct 2013 08:36:26 +0800 [thread overview]
Message-ID: <52671A0A.3020907@gtsys.com.hk> (raw)
In-Reply-To: <20131022121348.F30EE3811DA@gemini.denx.de>
Hi Wolfgang,
On Tuesday, October 22, 2013 08:13 PM, Wolfgang Denk wrote:
> Dear Chris Ruehl,
>
> I wrote:
>
>> If everything else fails, use "USE_PRIVATE_LIBGCC=y" on the make
>> command line.
>
> I mean: use "USE_PRIVATE_LIBGCC=yes" on the make command line.
after I set this option the build failed for
/uboot.d/u-boot-git/arch/arm/lib/libgcc.o -Map u-boot.map -o u-boot
fs/jffs2/libjffs2.o: In function `jffs2_1pass_build_lists':
/opt/cross_build/uboot.d/u-boot-git/fs/jffs2/jffs2_1pass.c:1441: undefined
reference to `__aeabi_uldivmod'
I mentioned this reference as "root of the evil" before :-)
Chris
>
>
> Best regards,
>
> Wolfgang Denk
>
--
GTSYS Limited RFID Technology
A01 24/F Gold King Industrial Bld
35-41 Tai Lin Pai Road, Kwai Chung, Hong Kong
Fax (852) 8167 4060 - Tel (852) 3598 9488
Disclaimer: http://www.gtsys.com.hk/email/classified.html
next prev parent reply other threads:[~2013-10-23 0:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 12:13 [U-Boot] v2013.10 failed build with jffs2 cmd Wolfgang Denk
2013-10-23 0:36 ` Chris Ruehl [this message]
2013-10-23 1:44 ` Chris Ruehl
2013-10-27 9:14 ` [U-Boot] [PATCH] JFFS2: Fix undefined reference to `__aeabi_uldivmod' error Wolfgang Denk
2013-10-27 9:46 ` Chris Ruehl
2013-10-27 10:01 ` Wolfgang Denk
2013-10-27 23:50 ` Chris Ruehl
2013-10-27 18:17 ` Daniel Schwierzeck
2013-10-27 20:07 ` Wolfgang Denk
2013-10-28 2:22 ` Chris Ruehl
2013-11-22 4:55 ` Gupta, Pekon
-- strict thread matches above, loose matches on Subject: below --
2013-10-22 2:15 [U-Boot] v2013.10 failed build with jffs2 cmd Chris Ruehl
[not found] ` <20131022060753.9F8EB380A62@gemini.denx.de>
2013-10-22 6:54 ` Chris Ruehl
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=52671A0A.3020907@gtsys.com.hk \
--to=chris.ruehl@gtsys.com.hk \
--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.