xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Chen Baozi <baozich@gmail.com>
To: Julien Grall <julien.grall@gmail.com>
Cc: xen-arm@lists.xen.org, ian.campbell@citrix.com,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Linking errors of Mini-OS for ARM32
Date: Mon, 10 Jun 2013 08:13:15 +0800	[thread overview]
Message-ID: <20130610001315.GA1714@cbz-workstation> (raw)
In-Reply-To: <CAF3u54B4tseyuU=ZP=3wJ__2iko_jHn=P5Kk9ueKP8wEM2NfBQ@mail.gmail.com>

On Sun, Jun 09, 2013 at 02:48:42PM +0100, Julien Grall wrote:
> On Sun, Jun 9, 2013 at 1:42 PM, Chen Baozi <baozich@gmail.com> wrote:
> > 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?
> 
> You need to provide an implementation for __aeabi_uldivmod.
> For this purpose, you can re-use xen/arch/arm/arm32/lib/lib1func.S

Thanks a lot.

A further question. I'm a litte curious that whether __aeabi_uldivmod is missing 
because of a toolchain bug or some other reasons? 

Cheers,

	Baozi

  parent reply	other threads:[~2013-06-10  0:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-09 12:42 Linking errors of Mini-OS for ARM32 Chen Baozi
2013-06-09 13:48 ` 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 [this message]
2013-06-10 10:06     ` 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=20130610001315.GA1714@cbz-workstation \
    --to=baozich@gmail.com \
    --cc=ian.campbell@citrix.com \
    --cc=julien.grall@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).