From: Steve Long <slong@rathaus.eclipse.co.uk>
To: gentoo-project@lists.gentoo.org
Subject: [gentoo-project] ABI deps and DEPEND labelling
Date: Tue, 19 Aug 2008 21:35:35 +0100 [thread overview]
Message-ID: <g8fav8$j69$1@ger.gmane.org> (raw)
Posting to project as I think this stuff needs input from users as well as
devs. (Many users have a lot of experience with embedded dev and ABI
quirks.)
Flameeyes posted here about ABI deps:
http://blog.flameeyes.eu/articles/2008/08/18/same-abi-and-any-abi-dependencies
..which reminded me a lot of:
http://bugs.gentoo.org/show_bug.cgi?id=201499
Not really fussed about how it's resolved, so long as we get some sort of
correct link dependency information (which compile-against is not.) OFC
that probably means we'll never get correct LDEPENDs but such is life ;)
What do others reckon about resolving ABI stuff, especially for cross-dev
and multi-lib/testing?
next reply other threads:[~2008-08-19 20:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 20:35 Steve Long [this message]
2008-08-19 20:45 ` [gentoo-project] ABI deps and DEPEND labelling Ciaran McCreesh
2008-08-21 15:54 ` [gentoo-project] " Steve Long
2008-08-21 16:07 ` Ciaran McCreesh
2008-08-23 15:06 ` [gentoo-project] " Steve Long
2008-08-19 20:52 ` [gentoo-project] " David Leverton
2008-08-21 16:27 ` [gentoo-project] " Steve Long
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='g8fav8$j69$1@ger.gmane.org' \
--to=slong@rathaus.eclipse.co.uk \
--cc=gentoo-project@lists.gentoo.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