From: Khem Raj <raj.khem@gmail.com>
To: McClintock Matthew-B29882 <B29882@freescale.com>
Cc: "openembedded-core@lists.openembedded.org oe-core layer"
<openembedded-core@lists.openembedded.org>
Subject: Re: perl install error
Date: Thu, 27 Sep 2012 20:43:06 -0700 [thread overview]
Message-ID: <C4E52DF7-ECBD-4411-9DA6-5E7F920FE747@gmail.com> (raw)
In-Reply-To: <70CC66F5C30A414DADDA6973E4CA391A6B4252@039-SN1MPN1-001.039d.mgd.msft.net>
On Sep 27, 2012, at 8:40 PM, McClintock Matthew-B29882 <B29882@freescale.com> wrote:
> Khem,
>
> I'm just not looking at a similiar issue. Do this:
>
just 'not' or just 'now' ?
> cat tmp/sstate-control/manifest-* | grep usr/lib/perl5
>
> And see which recipe is making this folder. It should be the perl
> recipe, first not some other recipe…
cat sstate-control/manifest-* | grep usr/lib/perl5
return nothing
>
> Side question are you using FSL layers?
yes
>
> -M
>
> On Thu, Sep 27, 2012 at 10:28 PM, Khem Raj <raj.khem@gmail.com> wrote:
>>
>> On Sep 27, 2012, at 8:22 PM, Khem Raj <raj.khem@gmail.com> wrote:
>>
>>> Hi
>>>
>>> On ppc64 I am getting
>>>
>>> | Warning: perl appears in your path in the following locations beyond where
>>> | we just installed it:
>>> | /work/yocto/poky/build/tmp/sysroots/x86_64-linux/usr/bin/perl-native/perl
>>> |
>>> | make[1]: Nothing to be done for `install.man'.
>>> | make[1]: Leaving directory `/work/yocto/poky/build/tmp/work/ppc64e5500-poky-linux/perl-5.14.2-r10/perl-5.14.2'
>>> | ln: failed to create symbolic link `/work/yocto/poky/build/tmp/work/ppc64e5500-poky-linux/perl-5.14.2-r10/image//usr/lib64/perl5': No such file or directory
>>> | ERROR: Function failed: do_install (see /work/yocto/poky/build/tmp/work/ppc64e5500-poky-linux/perl-5.14.2-r10/temp/log.do_install.6656 for further information)
>>> ERROR: Task 1679 (/work/yocto/poky/meta/recipes-devtools/perl/perl_5.14.2.bb, do_install) failed with exit code '1'
>>> NOTE: Tasks Summary: Attempted 4082 tasks of which 4057 didn't need to be rerun and 1 failed.
>>>
>>>
>>> It was working fine yesterday
>>> anyone else seeing it ?
>>
>>
>> If I revert
>>
>> perl: Fix nativesdk install path
>> Commit 38234f2e276356b1d77a87ceabc486107e336d19 tried to fix the sed
>> expressions by anchoring the left side of the search regexp to prevent
>> $prefix$prefix type expression in the perl config. For nativesdk this is
>> not enough. Adding anchors on both side fixes this.
>>
>> Signed-off-by: Christian Glindkamp <christian.glindkamp@taskit.de>
>> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>>
>>
>>
>> It works again
>>
>> Thanks
>> -Khem
>>
>>
>>
>> _______________________________________________
>> 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-09-28 3:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 3:22 perl install error Khem Raj
2012-09-28 3:28 ` Khem Raj
2012-09-28 3:40 ` McClintock Matthew-B29882
2012-09-28 3:43 ` Khem Raj [this message]
[not found] ` <70CC66F5C30A414DADDA6973E4CA391A6B43AC@039-SN1MPN1-001.039d.mgd.msft.net>
2012-09-28 4:18 ` Khem Raj
2012-09-28 4:23 ` McClintock Matthew-B29882
2012-09-28 4:38 ` Khem Raj
2012-09-28 5:04 ` McClintock Matthew-B29882
2012-09-28 13:22 ` Richard Purdie
2012-09-28 14:22 ` Khem Raj
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=C4E52DF7-ECBD-4411-9DA6-5E7F920FE747@gmail.com \
--to=raj.khem@gmail.com \
--cc=B29882@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox