From: Neuer User <auslands-kv@gmx.de>
To: yocto@yoctoproject.org
Subject: Re: Hmm, possible bug in poky?
Date: Fri, 06 Jun 2014 17:36:57 +0200 [thread overview]
Message-ID: <lmsn6p$dkl$1@ger.gmane.org> (raw)
In-Reply-To: <5391DA71.90402@mlbassoc.com>
Hi Gary, Hi Bruce
This is the directory layout:
Both recipes are extremely similar, only differ by a different git repo
and SRCREV. I might need to later have different patches for both
recipes, but currently everthing is identical. That's why I made an
include file.
.
├── linux-cubox-i-3.10.30
│ ├── brcmfmac4330-sdio.bin
│ ├── brcmfmac4330-sdio.txt
│ ├── defconfig
│ ├── dm-crypt.cfg
│ ├── leds.cfg
│ ├── mod-to-builtin.cfg
│ ├── networking.cfg
│ ├── no-caam.cfg
│ ├── touchscreen.cfg
│ ├── videoin.cfg
│ └── wlan.cfg
├── linux-cubox-i_3.10.30.bb
├── linux-cubox-i_3.10.30.inc
└── linux-cubox-i_3.10.30-linux4kix.bb
Am 06.06.2014 17:12, schrieb Gary Thomas:
> On 2014-06-06 08:56, Neuer User wrote:
>> Hi Bruce
>>
>> Thanks for the hint. I changed it, but the result is the same.
>>
>> Strange is really that it shows the directory as being searched through
>> but does not find the file that's contained?!
>>
>> Also, there are two "main" recipes, which both include the inc file.
>> This one throws warnings, but works:
>>
>> linux-cubox-i_3.10.30.bb
>>
>> This one throws warnings and then the error shown:
>>
>> linux-cubox-i_3.10.30-linux4kix.bb
>
> It's a bit hard to see what files you have where. Perhaps you
> could send a listing, e.g. for the standard Yocto kernel:
> $ tree meta/recipes-kernel/linux
> meta/recipes-kernel/linux
> ├── linux-dtb.inc
> ├── linux-dummy
> │ └── COPYING.GPL
> ├── linux-dummy.bb
> ├── linux-yocto_3.10.bb
> ├── linux-yocto_3.14.bb
> ├── linux-yocto_3.4.bb
> ├── linux-yocto-dev.bb
> ├── linux-yocto.inc
> ├── linux-yocto-rt_3.10.bb
> ├── linux-yocto-rt_3.14.bb
> ├── linux-yocto-rt_3.4.bb
> ├── linux-yocto-tiny_3.10.bb
> ├── linux-yocto-tiny_3.14.bb
> └── linux-yocto-tiny_3.4.bb
>
> Do this for each of the kernel recipes you are trying to use.
>
>>
>> Am I doing it right (now with the :=), or is there something
>> fundamentally wrong with the two recipes and the include file?
>>
>> Michael
>>
>> Am 06.06.2014 16:40, schrieb Bruce Ashfield:
>>> On 14-06-06 07:16 AM, Neuer User wrote:
>>>> I get the following error:
>>>>
>>>> WARNING: Failed to fetch URL file://defconfig, attempting MIRRORS if
>>>> available
>>>> ERROR: Fetcher failure: Unable to find file file://defconfig anywhere.
>>>> The paths that were searched were:
>>>>
>>>> /home/ubuntu/yocto/sources/meta-omnisonix/recipes-kernel/linux/linux-cubox-i-3.10.30/poky
>>>>
>>>>
>>>> ...
>>>>
>>>> /home/ubuntu/yocto/sources/meta-omnisonix/recipes-kernel/linux/files/arm
>>>>
>>>>
>>>> /home/ubuntu/yocto/sources/meta-omnisonix/recipes-kernel/linux/linux-cubox-i-3.10.30/
>>>>
>>>>
>>>>
>>>> /home/ubuntu/yocto/sources/meta-omnisonix/recipes-kernel/linux/linux-cubox-i-3.10.30-linux4kix/
>>>>
>>>>
>>>>
>>>> /home/ubuntu/yocto/sources/meta-omnisonix/recipes-kernel/linux/linux-cubox-i/
>>>>
>>>>
>>>>
>>>> /home/ubuntu/yocto/sources/meta-omnisonix/recipes-kernel/linux/files/
>>>> /home/ubuntu/yocto/downloads/
>>>> ERROR: Function failed: Fetcher failure for URL: 'file://defconfig'.
>>>> Unable to fetch URL from any source.
>>>>
>>>>
>>>> Now, the directory:
>>>>
>>>>
>>>> /home/ubuntu/yocto/sources/meta-omnisonix/recipes-kernel/linux/linux-cubox-i-3.10.30/
>>>>
>>>>
>>>>
>>>> which is listed above, contains the "missing" file ("defconfig").
>>>>
>>>> Hmm, strange...
>>>>
>>>>
>>>>
>>>> Here are my recipes:
>>>>
>>>> linux-cubox-i_3.10.30.inc:
>>>> ------------------------------------
>>>> inherit kernel
>>>> require recipes-kernel/linux/linux-yocto.inc
>>>>
>>>> SUMMARY = "Linaro Kernel 3.10.30 with additional machine specific
>>>> patches"
>>>>
>>>> SRCBRANCH ?= "linux-linaro-lsk-mx6"
>>>>
>>>> FILESEXTRAPATHS_prepend += "${THISDIR}/${PN}-3.10.30:"
>>>
>>> Have you tried this variant ?
>>>
>>> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.10.30:"
>>>
>>> You need the := in the assignment to have it evaluate immediately and
>>> pick up the directory of your bbappend (who's subdir is the one that
>>> contains the defconfig).
>>>
>>> Bruce
>>>
>>>
>>>>
>>>> SRC_URI = "file://defconfig \
>>>> file://videoin.cfg \
>>>> file://networking.cfg \
>>>> file://wlan.cfg \
>>>> file://dm-crypt.cfg \
>>>> file://no-caam.cfg \
>>>> file://leds.cfg \
>>>> file://mod-to-builtin.cfg \
>>>> file://brcmfmac4330-sdio.bin \
>>>> file://brcmfmac4330-sdio.txt \
>>>> "
>>>>
>>>> do_configure_append () {
>>>> cd ${S}
>>>> mkdir firmware/brcm
>>>> cp ../brcmfmac4330-sdio.bin ./firmware/brcm/
>>>> cp ../brcmfmac4330-sdio.txt ./firmware/brcm/
>>>> }
>>>>
>>>> COMPATIBLE_MACHINE = "(cubox-i)"
>>>>
>>>> KERNEL_IMAGETYPE_cubox-i = "zImage"
>>>> KERNEL_DEVICETREE_cubox-i = "imx6dl-cubox-i.dtb imx6q-cubox-i.dtb"
>>>>
>>>> SRCREV_machine = "${SRCREV}"
>>>> ------------------------------------
>>>>
>>>>
>>>> linux-cubox-i_3.10.30.bb:
>>>> ------------------------------------
>>>> include linux-cubox-i_3.10.30.inc
>>>>
>>>> SRCREV = "592b2d941dc3ecb6335d6820757340ffb5a192c8"
>>>> #SRCREV = "860304ab6e749777523f3714d18c4c7d39b728fa"
>>>> LOCALVERSION = "-cubox-i+SolidRun+${SRCPV}"
>>>>
>>>> SRC_URI +=
>>>> "git://github.com/SolidRun/linux-linaro-stable-mx6;branch=${SRCBRANCH}"
>>>> -------------------------------
>>>>
>>>>
>>>> linux-cubox-i_3.10.30-linux4kix.bb:
>>>> ------------------------------------
>>>> include linux-cubox-i_3.10.30.inc
>>>>
>>>> SRCREV = "a4ed70040f9dfdcdd6546a85c0477ecd1030e065"
>>>> LOCALVERSION = "-cubox-i+linux4kix+${SRCPV}"
>>>>
>>>> SRC_URI +=
>>>> "git://github.com/linux4kix/linux-linaro-stable-mx6.git;branch=${SRCBRANCH}"
>>>>
>>>>
>>>> ------------------------------------
>>>>
>>>>
>>>
>>
>>
>
next prev parent reply other threads:[~2014-06-06 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 11:16 Hmm, possible bug in poky? Neuer User
2014-06-06 14:40 ` Bruce Ashfield
2014-06-06 14:56 ` Neuer User
2014-06-06 15:12 ` Gary Thomas
2014-06-06 15:36 ` Neuer User [this message]
2014-06-06 20:59 ` Bruce Ashfield
2014-06-06 15:16 ` Bruce Ashfield
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='lmsn6p$dkl$1@ger.gmane.org' \
--to=auslands-kv@gmx.de \
--cc=yocto@yoctoproject.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.