From: Robert Yang <liezhi.yang@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] guile: fixed installed-vs-shipped error
Date: Thu, 8 Jan 2015 17:26:44 +0800 [thread overview]
Message-ID: <54AE4D54.1090603@windriver.com> (raw)
In-Reply-To: <1420708823.25779.81.camel@linuxfoundation.org>
On 01/08/2015 05:20 PM, Richard Purdie wrote:
> On Wed, 2015-01-07 at 06:55 -0800, Robert Yang wrote:
>> Fixed:
>> guile-2.0.11: guile: Files/directories were installed but not shipped
>> /usr/lib64/libguile-2.0*-gdb.scm [installed-vs-shipped]
>>
>> This is because when there is no file in the directory:
>> for f in libguile-2.0*; do
>> [snip]
>> done
>>
>> The f would be libguile-2.0* itself, make sure the libs are installed
>> firstly will fix the problem.
>>
>> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
>> ---
>> .../guile/files/libguile-Makefile.am-depends.patch | 39 ++++++++++++++++++++
>> meta/recipes-devtools/guile/guile_2.0.11.bb | 1 +
>> 2 files changed, 40 insertions(+)
>> create mode 100644 meta/recipes-devtools/guile/files/libguile-Makefile.am-depends.patch
>
> Not sure if this is as a result of this patch or a different issue but
> we saw:
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-x86-64-lsb/builds/153/steps/BuildImages_1/logs/stdio
>
> in a build containing this patch. Looks like some dependency is missing
> and its trying to install the lib twice?
OK, I will take a look it.
// Robert
>
> Cheers,
>
> Richard
>
>
>
next prev parent reply other threads:[~2015-01-08 9:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 14:55 [PATCH 0/1] guile: fixed installed-vs-shipped error (parallel issue) Robert Yang
2015-01-07 14:55 ` [PATCH 1/1] guile: fixed installed-vs-shipped error Robert Yang
2015-01-08 9:20 ` Richard Purdie
2015-01-08 9:26 ` Robert Yang [this message]
2015-01-08 23:39 ` Robert Yang
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=54AE4D54.1090603@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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