No no, myfile.tar.gz was a dummy name I used in this mail tree to
avoid deep explanation. As said in previous mail, I'm trying to build
quilt and I'm in trouble with its tar.gz source put into the directory
the tree shows. I've downloaded it by hand and put under files
directory, then I set FILESEXTRAPATHS inside the bbappend.

Il giorno 11/apr/2012, alle ore 15:02, Jaap de Jong
<jaap.dej...@nedap.com> ha scritto:

> There is no file named: myfile.tar.gz
> That it can't be found by bitbake is pretty clear then...
>
>
> On 04/11/2012 02:49 PM, Giuseppe Condorelli wrote:
>>> I'm obtaining this error trying to rebuild the poky-edison repository
>>> (http://downloads.yoctoproject.org/releases/yocto/yocto-1.1.1/poky-edison-6.
>>> 0.1.tar.bz2)
>>> and the error is happening trying to build quilt-native package (indeed I'm
>>> running ../script/bitbake -k core-image-sato), where I passed the tar.gz
>>> directly using the instructions below.
>>>
>>> This is the output of tree meta-yocto (snipped)
>>>
>>> meta-yocto
>>>     recipes-devtools
>>>          quilt
>>>               files
>>>        quilt-0.48.tar.gz
>>>    quilt-native_0.48.bbappend
>>>
>>> Best Regards,
>>> Giuseppe
>>>
>>>
>>> -----Original Message-----
>>> From: openembedded-devel-boun...@lists.openembedded.org
>>> [mailto:openembedded-devel-boun...@lists.openembedded.org] On Behalf Of Gary
>>> Thomas
>>> Sent: mercoledì 11 aprile 2012 13:06
>>> To: openembedded-devel@lists.openembedded.org
>>> Subject: Re: [oe] [oe-core] THISDIR usage
>>>
>>> On 2012-04-11 04:52, Giuseppe Condorelli wrote:
>>>> Many thanks for the reply, I tried the suggestion but I obtained this:
>>>>
>>>> "Unable to fetch URL file://myfile.tar.gz from any source"
>>>>
>>>> What's happening?
>>> Does your layer look like the pseudo tree quoted below?  Can you send the
>>> results of 'tree meta-giuseppe'?
>>>
>>> One way to get a glimpse of where bitbake is looking for your file is to use
>>> strace (GIANT hammer) like this:
>>>   % strace -o /tmp/xx.bb -f bitbake some-recipe
>>>   % grep myfile.tar.gz /tmp/xx.bb
>>> This way you can see the paths being searched.
>>>
>>>> Il giorno mercoledì 11 aprile 2012, Gary Thomas ha scritto:
>>>>
>>>>> On 2012-04-11 04:23, Giuseppe Condorelli wrote:
>>>>>
>>>>>> Hi, I moved to OE-Core (working on stable version dowloaded as tar
>>>>>> file from cgit.openembedded.org).
>>>>>> I'm in trouble trying to include a source through .bbappend file,
>>> located
>>>>>> under my meta-<personal>    subtree.
>>>>>>
>>>>>> FILESPATHBASE_prepend := "${THISDIR}/files:"
>>>>>> SRC_URI += "file://myfile.tar.gz"
>>>>>>
>>>>>> results in a no such file or directory. Please can you tell me if
>>>>>> I'm missing anything?
>>>>>>
>>>>> Assuming your tree looks something like this [partial]:
>>>>>
>>>>>  meta-giuseppe:
>>>>>    recipes:
>>>>>      some-recipe:
>>>>>        some-recipe_1.2.3.bbappend
>>>>>        files:
>>>>>          myfile.tar.gz
>>>>>
>>>>> Try using this instead
>>>>>  FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
>>> --
>>> ------------------------------------------------------------
>>> Gary Thomas                 |  Consulting for the
>>> MLB Associates              |    Embedded world
>>> ------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Openembedded-devel mailing list
>>> Openembedded-devel@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Reply via email to