public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH] fix compilation issue in arm cortex a8
Date: Tue, 05 Jan 2010 15:40:19 -0600	[thread overview]
Message-ID: <4B43B1C3.4000906@windriver.com> (raw)
In-Reply-To: <4B435794.3010603@gandalf.sssup.it>

Michael Trimarchi wrote:
> Hi,
> 
> this patch fix the compilation issue. Step to reproduce:
> 
> add CONFIG_YAFFS2 in overo defconfig and compile u-boot
> 
> Regards
> Michael
> 
> 

This is not an OMAP specific problem.
This problem will happen on all ARM platforms.

It would be better to understand why these unwind calls are being made and
to just not do them.

As this is an eabi problem.
Adding

void *__exidx_start;
void *__exidx_end;

To eabi_compat.c also "fixes" the link problem.
This may be a better place for the change than all the linker scripts

In general cases where libgcc is problem, you can build with

USE_PRIVATE_LIBGCC=yes

Trying this unfortunately has another link problem

fs/yaffs2/libyaffs2.a(yaffscfg.o): In function `yaffs_StartUp':
	fs/yaffs2/yaffscfg.c:185: undefined reference to `__aeabi_uldivmod'

This function could be added to lib_arm/_udivsi3.S or a new file if you
feel it is appropriate.

Tom

  reply	other threads:[~2010-01-05 21:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-05 15:15 [U-Boot] [RFC PATCH] fix compilation issue in arm cortex a8 Michael Trimarchi
2010-01-05 21:40 ` Tom [this message]
2010-01-07  8:01   ` Michael Trimarchi
2010-01-08 11:23   ` Michael Trimarchi

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=4B43B1C3.4000906@windriver.com \
    --to=tom.rix@windriver.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