From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: LEAD_SONAME?
Date: Thu, 27 Mar 2008 18:09:43 +0100 [thread overview]
Message-ID: <fsgkcn$n1t$1@ger.gmane.org> (raw)
In-Reply-To: <200803271752.07855.thomas.cooksey@trolltech.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Tom Cooksey schreef:
| On Thursday 27 March 2008 15:44:02 Holger Freyther wrote:
|> On Thursday 27 March 2008 12:17:41 Tom Cooksey wrote:
|>> I get a warning saying:
|>>
|>> NOTE: Multiple libraries (...) found and LEAD_SONAME not defined
|> this has to do with debian package renaming. This happens when
someone (e.g.
|> your distro as part of its policies) INHERITS the debian bbclass.
|>
|> What is happening:
|> Imagine I have a package foo and only install a libfoo.so.1.0.0 in the
|> libdir. AFAIK according to debian packaging policies the package gets
renamed
|> from foo to libfoo1. If you have more than one lib installed OE does
not know
|> which lib name to pick and will print the warning (debian.bbclass:83).
|
| Ok, well I'm not sure I like the idea of packages being renamed
outside my control,
| I wouldn't know which name to use in DEPENDS in other recipies.
OE takes care of that automagically.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFH69TXMkyGM64RGpERAky5AKCc5MQXVV0RxJNA4e5hlG3AaNjONgCfaSOo
vaKGmC/9xBygCzMToyC8DPY=
=Mnqv
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-03-27 17:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 11:17 LEAD_SONAME? Tom Cooksey
2008-03-27 12:30 ` LEAD_SONAME? Tom Cooksey
2008-03-27 14:44 ` LEAD_SONAME? Holger Freyther
2008-03-27 16:52 ` LEAD_SONAME? Tom Cooksey
2008-03-27 17:09 ` Koen Kooi [this message]
2008-03-27 17:13 ` LEAD_SONAME? Richard Purdie
2008-03-27 17:45 ` LEAD_SONAME? Tom Rini
2008-03-28 9:31 ` LEAD_SONAME? Richard Purdie
2008-03-27 17:40 ` LEAD_SONAME? Holger Freyther
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='fsgkcn$n1t$1@ger.gmane.org' \
--to=koen@dominion.kabel.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.