I have tried the different task separately.
do_fetch works, no recursive link created
do_kernel_checkout works, no recursive link created
do_kernel_configme works, no recursive link created
do_compile works, no recursive link created
do_compile_kernelmodules works, no recursive link created
do_install works, no recursive link created
do_package : Here it crashes. Th package subfolder is created and here
it creates the recursive link within the subfolder.
What does do_package do in detail? How can I further analyze the error.
/Markus
On 10.07.2014 17:46, Bruce Ashfield wrote:
On 14-07-10 07:11 AM, Dr. Markus Eich wrote:
Thank you Bruce, that did the trick. But I am facing a new problem while
using bitbake for the build process.
I have checked to build the odroid kernel with a standard crosscompiler
tool chain and it works without any problems.
When I do the same with the bitbake toolchain (bitbake virtual/kernel),
it somehow creates a recursive link in the folder
package/usr/src/kernel/drivers/gpu/arm/mali400/ump/arch/arch-release ->
arch-release
This causes a crash in the build system.
Compilation runs fine though. This error seems to be within do_package.
I have removed the link, but somehow it is created automatically.
Any ideas?
Nothing off the top of my head. That link would be created by the kernel
build, and not by bitbake or the oe-core kernel build classes.
I'd start by looking at the kernel's makefiles and seeing where the
link is being created.
Do specific tasks work ? i.e. is that happening during unpack/patch, or
during compilation.
Bruce
/Markus
On 09.07.2014 14:44, Bruce Ashfield wrote:
On 14-07-09 05:38 AM, Dr. Markus Eich wrote:
Dear all,
I work on the process to compile odroid xu kernel with yocto/bitbake
In the kernel sources (from hardkernel) I have the corresponding
defconfig file, i.e. in the git folder
/arch/arm/configs/odroidxu_ubuntu_defconfig.
How can I tell bitbake in my recipe to use
"odroidxu_ubuntu_defconfig"?
To trigger the oe-core kernel processing to use the defconfig, you need
to put that defconfig in your SRC_URI.
Which means you should grab a copy of that from the kernel tree, and
in the same directory structure as your kernel recipe.
See meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb for an
example.
Cheers,
Bruce
My recipe looks as follow:
===
require recipes-kernel/linux/linux-yocto.inc
KERNEL_IMAGETYPE = "uImage"
COMPATIBLE_MACHINE = "odroid-xu"
LINUX_VERSION = "3.4.91"
LINUX_VERSION_EXTENSION = "-custom"
FILESEXTRAPATHS_prepend := "${THISDIR}/linux-hardkernel-3.4:"
S = "${WORKDIR}/git"
# from where to fetch the kernel
KERNEL_REPO_OWNER ??= "hardkernel"
KERNEL_REPO_URI ??= "git://github.com/${KERNEL_REPO_OWNER}/linux.git"
KBRANCH = "odroidxu-3.4.y"
SRCREV = "${AUTOREV}"
KV = "3.4.91"
PV = "${KV}+gitr${SRCPV}"
LOCALVERSION ?= ""
SRC_URI = " \
${KERNEL_REPO_URI};nocheckout=1;branch=${KBRANCH} \
"
PACKAGES =+ "kernel-headers"
FILES_kernel-headers = "${exec_prefix}/src/linux*"
===
Cheers,
Markus
--
Dr.-Ing. Markus Eich
Senior Researcher
Marine Inspection Robotics
Space Robotics
Besuchsadresse der Nebengeschäftstelle:
DFKI GmbH
Robotics Innovation Center
Robert-Hooke-Straße 5
28359 Bremen, Germany
Postadresse der Hauptgeschäftsstelle Standort Bremen:
DFKI GmbH
Robotics Innovation Center
Robert-Hooke-Straße 1
28359 Bremen, Germany
Tel.: +49 421 178 45-4105
Zentrale: +49 421 178 45-0
Fax: +49 421 178 45-4150 (Faxe bitte namentlich kennzeichnen)
E-Mail: markus.e...@dfki.de
Weitere Informationen: http://www.dfki.de/robotik
-----------------------------------------------------------------------
Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern
Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster
(Vorsitzender) Dr. Walter Olthoff
Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
Amtsgericht Kaiserslautern, HRB 2313
Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
USt-Id.Nr.: DE 148646973
Steuernummer: 19/673/0060/3
-----------------------------------------------------------------------
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
