Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] can't resolve symbol '__cxa_atexit'
Date: Wed, 10 Feb 2010 08:32:50 +0100	[thread overview]
Message-ID: <20100210083250.7cc2a7c6@surf> (raw)
In-Reply-To: <6fff79821002091835j7a1499f4n977fcf81dbe381b8@mail.gmail.com>

On Wed, 10 Feb 2010 08:05:07 +0530
Souvik Ghosh <mailtosouvik@gmail.com> wrote:

> I was compiling buildroot v2009.02 for ARM. The gcc, uclibc and
> binutils version I selected are 4.3.2, 0.9.30 and 2.19 respectively.
> With this toolchain the compilation of my source is going on fine but
> it produces "*can't resolve symbol '__cxa_atexit'" *error at runtime.
> Can anyone please point me what I am missing and what is reason of
> this cause?

Could you try with a more recent Buildroot version, say 2009.11 ? If it
still fails, please send your .config.

Did you really recompile *all* your applications with the toolchain
generated by Buildroot ? Remember that uClibc doesn't provide any kind
of ABI backward compatibility, so you have to recompile your
applications with exactly the toolchain that uses the C library that is
on the target.

Did you use the default uClibc configuration file, or did you customize
it somehow ?

Cheers,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2010-02-10  7:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-10  2:35 [Buildroot] can't resolve symbol '__cxa_atexit' Souvik Ghosh
2010-02-10  7:32 ` Thomas Petazzoni [this message]
2010-02-10 11:00   ` Nuno Pereira
  -- strict thread matches above, loose matches on Subject: below --
2007-08-28 21:07 [Buildroot] Can't " Nathanael D. Noblet
2007-08-28 22:19 ` Nathanael D. Noblet

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=20100210083250.7cc2a7c6@surf \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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