[meta-intel] unionfs patch error

Bruce Ashfield bruce.ashfield at gmail.com
Tue Apr 2 13:19:45 PDT 2013 

On Tue, Apr 2, 2013 at 1:14 PM, Wenholz, Brian (GE Healthcare)
<Brian.Wenholz at med.ge.com> wrote:
> Bruce,
>
> I added it in the kernel features append variable in my customized BSP layer. The layer is a modified copy of the meta-crownbay layer since I got stumped trying to simply extend it as a new machine and image. The image recipe is below. I put unionfs into the KERNEL_FEATURES_sunrise_append variable. I tried on both sides of the emgd and vesafb entries.
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
>
> COMPATIBLE_MACHINE_sunrise = "sunrise"
> KMACHINE_sunrise = "crownbay"
> KBRANCH_sunrise = "standard/crownbay"
> KERNEL_FEATURES_sunrise_append = "unionfs  features/drm-emgd/drm-emgd-1.16 cfg/vesafb "

Aha. I was doing about three things at once this morning and didn't notice that
you were talking 3.8 versus the 3.4 kernel. I had made the substitution of the
3.4 kernel in my mind when I answered.

For the 3.8 kernel, unionfs wasn't being actively maintained when I
was working through
the uprev and the VFS changes made the port challenging. Since other
union* filesystem
types were either more active (aufs), or again attempting to be
mainlined (overlayfs), I
merged aufs for the union mount solution.

I can check again for a unionfs 3.8* functional port again and
re-enable the support, but
for now,  perhaps aufs will serve your needs ?

Bruce

>
> SRCREV_meta_sunrise = "c2ed0f16fdec628242a682897d5d86df4547cf24"
> SRCREV_machine_sunrise = "b170394a475b96ecc92cbc9e4b002bed0a9f69c5"
> SRCREV_emgd_sunrise = "caea08c988e0f41103bbe18eafca20348f95da02"
>
> SRC_URI_sunrise = "git://git.yoctoproject.org/linux-yocto-3.8.git;protocol=git;nocheckout=1;branch=${KBRANCH},${KMETA},emgd-1.16;name=machine,meta,emgd"
> SRC_URI_sunrise += " file://multi-touch.cfg \
>                      file://egalax-7200.patch \
>                      file://networking.cfg \
>                      file://gpio.cfg \
>                      file://efi.cfg \
>                      "
>
> #                     file://graphics.cfg \
> #
>
> PRINC := "${@int(PRINC) + 1}"
>
> -----Original Message-----
> From: Bruce Ashfield [mailto:bruce.ashfield at gmail.com]
> Sent: Tuesday, April 02, 2013 11:54 AM
> To: Wenholz, Brian (GE Healthcare)
> Cc: meta-intel at yoctoproject.org
> Subject: Re: [meta-intel] unionfs patch error
>
> On Tue, Apr 2, 2013 at 10:21 AM, Wenholz, Brian (GE Healthcare) <Brian.Wenholz at med.ge.com> wrote:
>> I am building a Crownbay based BSP and need unionfs support in the kernel.
>> When enabling the unionfs kernel feature and building I get a patch
>> error due to extra new lines inserted by
>> "unionfs-introduce-unionfs-2.5.11-core-support.patch". Full output below.
>>
>>
>>
>> 2 Questions:
>>
>> 1>   Is this a new issue that I should open a BugZilla report on, or a
>> 1> known
>> issue?
>
> Neither of the above. It's likely just a nuance of how you are trying to enable the functionality.
>
>>
>> 2>   As a newbie to Yocto, how do I force the patch to apply since the
>> 2> new
>> lines should not cause a problem farther down the build cycle?
>
> unionfs is always applied to the tree, hence why any effort to re-apply the patch will fail.
>
> How did you try and enable it ? It should just be a matter of adding a config fragment with the options of your requirements.
>
> Cheers,
>
> Bruce
>
>>
>>
>>
>> Any help would be appretiated.
>>
>>
>>
>> Brian Wenholz
>>
>>
>>
>> bitbake linux-yocto -c menuconfig
>>
>> WARNING: Host distribution "LinuxMint-13" has not been validated with
>> this version of the build system; you may possibly experience
>> unexpected failures. It is recommended that you use a tested distribution.
>>
>> Loading cache: 100%
>> |#####################################################################
>> |###############################################|
>> ETA:  00:00:00
>>
>> Loaded 1142 entries from dependency cache.
>>
>>
>>
>> Build Configuration:
>>
>> BB_VERSION        = "1.17.1"
>>
>> BUILD_SYS         = "i686-linux"
>>
>> NATIVELSBSTRING   = "LinuxMint-13"
>>
>> TARGET_SYS        = "i586-poky-linux"
>>
>> MACHINE           = "sunrise"
>>
>> DISTRO            = "poky"
>>
>> DISTRO_VERSION    = "1.3+snapshot-20130401"
>>
>> TUNE_FEATURES     = "m32 core2"
>>
>> TARGET_FPU        = ""
>>
>> meta
>>
>> meta-yocto
>>
>> meta-yocto-bsp    = "master:4da406cd50cf02a63ed76810a670aba1eb561c79"
>>
>> meta-intel        = "master:7a5e19e0c7d5967ef7b003ab775b7210c0ee16d7"
>>
>> meta-sunrise      = "master:4da406cd50cf02a63ed76810a670aba1eb561c79"
>>
>>
>>
>> NOTE: Resolving any missing task queue dependencies
>>
>> NOTE: Preparing runqueue
>>
>> NOTE: Executing SetScene Tasks
>>
>> NOTE: Executing RunQueue Tasks
>>
>> ERROR: Function failed: do_patch (see
>> /media/sf_ClearCaseViews/yocto/yocmnt/poky/build-sunrise/tmp/work/sunr
>> ise-poky-linux/linux-yocto/3.8.1+gitAUTOINC+c2ed0f16fdec628242a682897d
>> 5d86df4547cf24_b170394a475b96ecc92cbc9e4b002bed0a9f69c5-r5.0/temp/log.
>> do_patch.31925
>> for further information)
>>
>> ERROR: Logfile of failure stored in:
>> /media/sf_ClearCaseViews/yocto/yocmnt/poky/build-sunrise/tmp/work/sunr
>> ise-poky-linux/linux-yocto/3.8.1+gitAUTOINC+c2ed0f16fdec628242a682897d
>> 5d86df4547cf24_b170394a475b96ecc92cbc9e4b002bed0a9f69c5-r5.0/temp/log.
>> do_patch.31925
>>
>> Log data follows:
>>
>> | DEBUG: Executing shell function do_patch
>>
>> | Deleted branch meta-temp (was 37fdb0c).
>>
>> | NOTE: feature features/kprobes/kprobes.scc is included multiple
>> | times
>> (/media/sf_ClearCaseViews/yocto/yocmnt/poky/build-sunrise/tmp/work/sun
>> rise-poky-linux/linux-yocto/3.8.1+gitAUTOINC+c2ed0f16fdec628242a682897
>> d5d86df4547cf24_b170394a475b96ecc92cbc9e4b002bed0a9f69c5-r5.0/linux/me
>> ta/cfg/kernel-cache/features/systemtap)
>>
>> | NOTE: feature ipsec.scc is included multiple times
>> (/media/sf_ClearCaseViews/yocto/yocmnt/poky/build-sunrise/tmp/work/sun
>> rise-poky-linux/linux-yocto/3.8.1+gitAUTOINC+c2ed0f16fdec628242a682897
>> d5d86df4547cf24_b170394a475b96ecc92cbc9e4b002bed0a9f69c5-r5.0/linux/me
>> ta/cfg/kernel-cache/cfg/net)
>>
>> | [INFO] validating against known patches  (crownbay-standard-meta)
>>
>> fatal: A branch named 'eg20t' already exists.        ] (-)(70 %))
>>
>> ./meta/patches/standard/crownbay/links/kernel-cache/features/unionfs/unionfs-introduce-unionfs-2.5.11-core-support.patch:476:
>> new blank line at EOF.
>>
>> | +
>>
>> | Context reduced to (1/1) to apply fragment at 7871
>>
>> | Context reduced to (1/1) to apply fragment at 489
>>
>> | Context reduced to (2/2) to apply fragment at 2146
>>
>> | Context reduced to (2/2) to apply fragment at 4125
>>
>> | error: include/linux/magic.h: does not exist in index
>>
>> | error: patch failed: include/linux/namei.h:84
>>
>> | error: include/linux/namei.h: patch does not apply
>>
>> |
>> ./meta/patches/standard/crownbay/links/kernel-cache/features/unionfs/unionfs-introduce-unionfs-2.5.11-core-support.patch:11476:
>> new blank line at EOF.
>>
>> | +
>>
>> | To force apply this patch, use 'guilt push -f'
>>
>> | [ERROR] unable to complete push
>>
>> | pending patches are:
>>
>> |
>> links/kernel-cache/features/unionfs/unionfs-introduce-unionfs-2.5.11-c
>> ore-support.patch
>>
>> |
>> links/kernel-cache/features/unionfs/unionfs-replace-d_alloc_root-with-
>> d_make_root.patch
>>
>> | links/kernel-cache/features/unionfs/unionfs-v3.4-build-fixups.patch
>>
>> |
>> links/kernel-cache/features/unionfs/unionfs-update-unionfs-fork-to-ali
>> gn-with-mainline.patch
>>
>> |
>> links/kernel-cache/features/unionfs/unionfs-restore-FD_-utility-define
>> s.patch
>>
>> | ERROR. could not update git tree
>>
>> | ERROR. Could not apply patches for crownbay.
>>
>> |        Patch failures can be resolved in the devshell (bitbake -c
>> | devshell
>> linux-yocto)
>>
>> | ERROR: Function failed: do_patch (see
>> /media/sf_ClearCaseViews/yocto/yocmnt/poky/build-sunrise/tmp/work/sunr
>> ise-poky-linux/linux-yocto/3.8.1+gitAUTOINC+c2ed0f16fdec628242a682897d
>> 5d86df4547cf24_b170394a475b96ecc92cbc9e4b002bed0a9f69c5-r5.0/temp/log.
>> do_patch.31925
>> for further information)
>>
>> ERROR: Task 3
>> (/media/sf_ClearCaseViews/yocto/yocmnt/poky/meta/recipes-kernel/linux/
>> linux-yocto_3.8.bb,
>> do_patch) failed with exit code '1'
>>
>> NOTE: Tasks Summary: Attempted 233 tasks of which 228 didn't need to
>> be rerun and 1 failed.
>>
>> No currently running tasks (233 of 236)
>>
>>
>>
>> Summary: 1 task failed:
>>
>>
>> /media/sf_ClearCaseViews/yocto/yocmnt/poky/meta/recipes-kernel/linux/l
>> inux-yocto_3.8.bb,
>> do_patch
>>
>> Summary: There was 1 WARNING message shown.
>>
>> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>>
>>
>> _______________________________________________
>> meta-intel mailing list
>> meta-intel at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-intel
>>
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"



--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"

More information about the meta-intel mailing list