Scratch that. It builds correctly but still fails in a console-image at
do_populate_sysroot (hair pulling stage).

-Matt


On Fri, May 31, 2013 at 3:10 AM, Matthew Hudson <hexs...@gmail.com> wrote:

>
> Well I have been fighting with this for a few days. I had done several -f
> to rebuild to no avail. I did a cleanall then -f and it completed without
> the directory mangling.
>
> -Matt
>
>
>
>
> On Thu, May 30, 2013 at 5:40 PM, Matthew Hudson <hexs...@gmail.com> wrote:
>
>>
>>
>> /mnt/bdd/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/i686-linux/libxml-parser-perl-native-2.41-r3/sysroot-destdir///mnt/bdd/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/sysroots/i686-linux
>>
>> This is the source directory that do_populate_sysroot is getting from
>> somewhere. I am trying to track down how this directory is being mangled
>> within the classes to determine why tar is failing (as per a previous post
>> I've made):
>>
>> log.do_populate_sysroot.13926:CalledProcessError: Command 'tar -cf - -C
>> /mnt/bdd/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/i686-linux/libxml-parser-perl-native-2.41-r3/sysroot-destdir///mnt/bdd/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/sysroots/i686-linux
>> -ps . | tar -xf - -C
>> /mnt/bdd/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/sysroots/i686-linux'
>> returned non-zero exit status 2 with output tar:
>> /mnt/bdd/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/i686-linux/libxml-parser-perl-native-2.41-r3/sysroot-destdir///mnt/bdd/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/sysroots/i686-linux:
>> Cannot chdir: No such file or directory
>>
>> I could quite easily be looking in the wrong place, but answers do no
>> readily come from developers in areas they have no interest in and it seems
>> someone had drawn the same conclusion I had as there are commented bb.debug
>> lines in the same areas I have been tracking into.
>>
>> -Matt
>>
>>
>>
>> On Thu, May 30, 2013 at 5:14 PM, Gary Thomas <g...@mlbassoc.com> wrote:
>>
>>> On 2013-05-30 14:09, Matthew Hudson wrote:
>>>
>>>> angstromv2012.12
>>>>
>>>> That is the case unless I change a class in openembedded-core/meta/**
>>>> classes,
>>>> then it seems to flush the cache and start over.
>>>>
>>>
>>> Indeed so, and quite correctly so!  In general you should not need to
>>> change core classes.
>>>
>>> What kind of changes have you needed?  Why could not those changes be
>>> made to recipes and/or using .bbappend?
>>>
>>>
>>>  On Thu, May 30, 2013 at 6:10 AM, Gary Thomas <g...@mlbassoc.com> wrote:
>>>>
>>>>  On 2013-05-30 04:58, Matthew Hudson wrote:
>>>>>
>>>>>  I'm trying to track down the libxml-parser-perl issue.
>>>>>>
>>>>>> When I add some debugging code into a .bb it parses all of the recipes
>>>>>> again. I'm not using a blazingly fast box to do this and it gets hung
>>>>>> at
>>>>>> 67
>>>>>> - 72% at times (Ctrl-C & terminal 'reset' required). It continues from
>>>>>> where it left off but this process can take hours :/
>>>>>>
>>>>>> I'd like to be able to make a change and just execute:
>>>>>>
>>>>>> bitbake libxml-parser-perl -c populate_sysroot
>>>>>>
>>>>>> without parsing the entire set of recipes every time.
>>>>>>
>>>>>> If there a way to do this?
>>>>>>
>>>>>>
>>>>> What version of bitbake and metadata are you using?
>>>>>
>>>>> Once fully parsed, it should not be necessary to run this again
>>>>> as the data is cached.  Subsequent runs should be quite zippy.
>>>>>
>>>>
>>> --
>>> ------------------------------**------------------------------
>>> Gary Thomas                 |  Consulting for the
>>> MLB Associates              |    Embedded world
>>> ------------------------------**------------------------------
>>>
>>> ______________________________**_________________
>>> Angstrom-distro-devel mailing list
>>> Angstrom-distro-devel@**linuxtogo.org<Angstrom-distro-devel@linuxtogo.org>
>>> http://lists.linuxtogo.org/**cgi-bin/mailman/listinfo/**
>>> angstrom-distro-devel<http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel>
>>>
>>
>>
>
_______________________________________________
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Reply via email to