From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: adding package nss in rootfs failed with dependency "/usr/local/bin/perl"
Date: Tue, 24 Apr 2012 10:21:05 -0500 [thread overview]
Message-ID: <4F96C4E1.9000508@windriver.com> (raw)
In-Reply-To: <CAAA4K6J1SNRCr0uM1tT=DjyV47mk-KqGUZjT+B8qgujANw9ZTQ@mail.gmail.com>
On 4/24/12 8:23 AM, Jegan Chandru wrote:
> Hi,
>
> I have cross compiled NSS 3.13.1 for x86 64 bit environment, but when I try to
> add NSS package in rootfs, i am getting the following error,
>
> /error: Failed dependencies:
> /usr/local/bin/perl is needed by nss-3.13.1-r0.x86_64/
>
> I know perl is needed for nss, but the path which is trying to look perl, is
> quite confusing me, for perl doesn't exist in that location at all. Can anyone
> please tell me whats going on here and what have I missed?
This is a bug in the nss package. It has an executable shell script that has a:
#! /usr/local/bin/perl
in it, which causes RPM to add a dependency on that specific path, and nothing
is providing the path.
The fix is either, decide this is a sample/demo shell script and remove it from
the nss package -- or fix the script to use the proper perl location of
"${bindir}/perl"
> P.S: I am using Yocto-1.1.1 and Ubuntu host-11.10 64 bit.
--Mark
> Thanks all for your help,
> JC
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2012-04-24 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 13:23 adding package nss in rootfs failed with dependency "/usr/local/bin/perl" Jegan Chandru
2012-04-24 15:21 ` Mark Hatle [this message]
2012-04-25 8:54 ` Jegan Chandru
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=4F96C4E1.9000508@windriver.com \
--to=mark.hatle@windriver.com \
--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 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.