All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Blackfin toolchain question
Date: Wed, 11 Nov 2009 22:27:26 +0000 (UTC)	[thread overview]
Message-ID: <hdfdoe$kj7$1@ger.gmane.org> (raw)

Hello,

I'm currently trying to restore/update blackfin toolchain. One of the major problems I've stumbled upon
are versioned scripts/export symbols. Basically there are lot's of software starting from g++ itself
that have symbol versioning scripts. The problem is that blackfin arch prepends all symbols with underscore,
thus breaking all that scripts.

My first intention was to follow the alsa-libs approach: handle all prefixing on package-per-package basis.
However that would be a nigtmare.

My current intention (that at least partially works) is to make libtool (when it's used) generate correct
versioning scripts and resort to package-per-package updating after that.

The problem comes from C++ world, where versioning script can contain unmangled name, but it's demangled
name that should be prefixed with underscore.

So I have a bit hackish idea: maybe it's better to hack ld to accept scripts w/o underscores and prefix all
symbols with it? This will eliminate most of changes. The question is if this patch is acceptable for OE?
Does this approach sound too hackish?

-- 
With best wishes
Dmitry





             reply	other threads:[~2009-11-11 22:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-11 22:27 Dmitry Eremin-Solenikov [this message]
2009-11-12  1:17 ` Blackfin toolchain question Holger Hans Peter Freyther
2009-11-12 10:19   ` Dmitry Eremin-Solenikov
2009-11-12 11:52 ` Phil Blundell

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='hdfdoe$kj7$1@ger.gmane.org' \
    --to=dbaryshkov@gmail.com \
    --cc=openembedded-devel@lists.openembedded.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.