From: Chen Baozi <baozich@gmail.com>
To: ian.campbell@citrix.com
Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org
Subject: Linking errors of Mini-OS for ARM32
Date: Sun, 9 Jun 2013 20:42:13 +0800 [thread overview]
Message-ID: <20130609124213.GA19123@cbz-workstation> (raw)
Hi Ian,
Since finishing the very beginning setup assembly, I was turning to adding
necessary headers and empty functions to build the binary. After introducing
those bit operations, spinlocks etc., I thought I have a basic framework to
pass the first build. However, when comming to the final linking stage,
there are errors:
arm-linux-gnueabihf-ld -T arch/arm/minios-arm32.lds
/home/cbz/src/xen/extras/mini-os/mini-os.o -o
//home/cbz/src/xen/extras/mini-os/mini-os
/home/cbz/src/xen/extras/mini-os/mini-os.o: In function `init_blkfront':
/home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod'
/home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod'
/home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod'
/home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod'
/home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod'
/home/cbz/src/xen/extras/mini-os/mini-os.o:/home/cbz/src/xen/extras/mini-os/blkfront.c:122: more undefined references to `__aeabi_uldivmod' follow
/home/cbz/src/xen/extras/mini-os/mini-os.o:(.ARM.exidx+0x0): undefined reference to `__aeabi_unwind_cpp_pr0'
/home/cbz/src/xen/extras/mini-os/mini-os.o:(.ARM.exidx+0x50): undefined reference to `__aeabi_unwind_cpp_pr0'
make: *** [/home/cbz/src/xen/extras/mini-os/mini-os] Error 1
I googled that error message. Some has mentioned that add "-fno-exceptions
-fno-unwind tables" could sovle the problem. I tried, but got the same
errors.
Any ideas?
BTW, after pass my first build, I would consider implementing support in the
toolstack for generating a DTB for guest on ARM platform.
Baozi
next reply other threads:[~2013-06-09 12:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-09 12:42 Chen Baozi [this message]
2013-06-09 13:48 ` Linking errors of Mini-OS for ARM32 Julien Grall
2013-06-09 14:19 ` Tim Deegan
2013-06-10 0:14 ` Chen Baozi
2013-06-10 13:44 ` [XenARM] " Stefano Stabellini
2013-06-10 0:13 ` Chen Baozi
2013-06-10 10:06 ` [XenARM] " Julien Grall
2013-07-12 13:14 ` Stefano Stabellini
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=20130609124213.GA19123@cbz-workstation \
--to=baozich@gmail.com \
--cc=ian.campbell@citrix.com \
--cc=xen-arm@lists.xen.org \
--cc=xen-devel@lists.xen.org \
/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.