On Tue, 2014-04-15 at 15:43 -0400, Denys Dmytriyenko wrote:
> I don't yet know what is going on, but building in the same directory with
> sources (B = S) makes it work regarless of the path length:
>
> /OE/RAM/poky-111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111/22222222222222222222222222222222222222222222222222222222222222222222/3333333333333333333333333333333333333333333333333333/tmp/work/beaglebone-poky-linux-gnueabi/linux-yocto/3.14+gitAUTOINC+928d7b2dda_0143c6ebb4-r0/linux
>
> So, I just commented out setting kernel-specific B in linux-yocto.inc and any
> kernel now boots with long path:
>
> #B = "${WORKDIR}/linux-${PACKAGE_ARCH}-${LINUX_KERNEL_TYPE}-build"
>
> I'm copying Richard and Bruce directly to see if they may have a quick
> insight
> and/or accept it as a workaround for the release. I'll keep digging further,
> but if anyone cares to verify the above workaround works for them, I would
> appreciate. Thanks!
I'm travelling and don't have hardware so I'm limited in what I can look
at right now. I suspect this workaround "works" because it makes the
"beaglebone-standard-build" extra characters on the path. I have a
feeling your -1111111 test above may have reused sstate or something
like that and given misleading results. I'd be interested in the vmlinux
file from the build above to see if the poky-111111 pathnames are in
there (they get stripped out when you create the zImage).
Cheers,
Richard
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
