From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/6] gmp: also generate the libgmpcxx library
Date: Thu, 20 Oct 2011 10:01:17 +0100 [thread overview]
Message-ID: <1319101278.22985.258.camel@phil-desktop> (raw)
In-Reply-To: <4E9FD2B2.5000508@intel.com>
On Thu, 2011-10-20 at 00:50 -0700, Saul Wold wrote:
> The example case I found was a coreutils package that was built prior to
> this change failed to fulfill it's dependencies after this change when
> creating an image. If I rebuild coreutils with the newer gmp build,
> then all is well, I think we need to understand this better before
> making this change.
>
> Did something else change in the packaging that would cause use to look
> the mapping above?
If you've now got two DSOs in one output package (which it sounds like
you might have, since libgmpcxx was apparently added) then the autonamer
will be defeated. They need to go in separate PACKAGES for that to work
out right.
p.
next prev parent reply other threads:[~2011-10-20 9:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 0:30 [PATCH 0/6] recipe upgrades + some fixes nitin.a.kamble
2011-10-19 0:30 ` [PATCH 1/6] x86 tune files: set baselib for x32 tune as libx32 nitin.a.kamble
2011-10-19 0:30 ` [PATCH 2/6] gmp: also generate the libgmpcxx library nitin.a.kamble
2011-10-20 7:50 ` Saul Wold
2011-10-20 8:01 ` Koen Kooi
2011-10-20 9:01 ` Phil Blundell [this message]
2011-10-21 6:04 ` Kamble, Nitin A
2011-10-21 7:54 ` Saul Wold
2011-10-21 16:54 ` Kamble, Nitin A
2011-10-19 0:30 ` [PATCH 3/6] python-scons: upgrade from 2.0.1 to 2.1.0 nitin.a.kamble
2011-10-19 0:30 ` [PATCH 4/6] python-dbus: upgrade from 0.83.2 to 0.84.0 nitin.a.kamble
2011-10-19 0:30 ` [PATCH 5/6] libxml-parser-perl: upgrade from 2.40 to 2.41 nitin.a.kamble
2011-10-19 0:31 ` [PATCH 6/6] distro-tracking: update data for some toolchain recipes nitin.a.kamble
2011-10-20 17:12 ` [PATCH 0/6] recipe upgrades + some fixes Saul Wold
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=1319101278.22985.258.camel@phil-desktop \
--to=philb@gnu.org \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox