[yocto] Creating a new recipe

Giuseppe Di Guglielmo giuseppe.diguglielmo at gmail.com
Fri May 5 10:24:21 PDT 2017


I made some further steps.

I attach the layer package that I am creating. You can add it to
conf/bblayers.conf.

The error that I the following. Let me know what you thing of it.

Thank you,
Giuseppe

$ bitbake bazel
Parsing recipes: 100%
|#################################################################################################################################################################################################|
Time: 0:00:32
Parsing of 1774 .bb files complete (0 cached, 1774 parsed). 2490 targets,
149 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION        = "1.32.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "universal-4.8"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "zc702-zynq7"
DISTRO            = "poky"
DISTRO_VERSION    = "2.2.1"
TUNE_FEATURES     = "arm armv7a vfp thumb neon       callconvention-hard
    cortexa9"
TARGET_FPU        = "hard"
meta              = "morty:924e576b8930fd2268d85f0b151e5f68a3c2afce"
meta-xilinx       = "morty:1ddfc0ba94f597822e619395fa0b35fb322e26af"
meta-poky
meta-tensorflow   = "morty:924e576b8930fd2268d85f0b151e5f68a3c2afce"
meta-xilinx-tools = "rel-v2017.1:64847a5afcffcb73e4bcf2137911819b55537308"
meta-yocto-bsp    = "morty:924e576b8930fd2268d85f0b151e5f68a3c2afce"
meta-oe
meta-python       = "morty:fe5c83312de11e80b85680ef237f8acb04b4b26e"
meta-java         = "HEAD:67e48693501bddb80745b9735b7b3d4d28dce9a1"
workspace         = "<unknown>:<unknown>"

Initialising tasks: 100%
|##############################################################################################################################################################################################|
Time: 0:00:01
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: bazel-0.4.5-r0 do_compile: Function failed: do_compile (log file is
located at
/home/giuseppe/research/projects/zynq/yocto/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/bazel/0.4.5-r0/temp/log.do_compile.4221)
ERROR: Logfile of failure stored in:
/home/giuseppe/research/projects/zynq/yocto/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/bazel/0.4.5-r0/temp/log.do_compile.4221
Log data follows:
| DEBUG: Executing shell function do_compile
| INFO: You can skip this first step by providing a path to the bazel
binary as second argument:
| INFO:    ./compile.sh compile /path/to/bazel
| �  Building Bazel from scratch.......
| �  Building Bazel with Bazel.
| .WARNING: /tmp/bazel_tTNeGhsI/out/external/bazel_tools/WORKSPACE:1:
Workspace name in /tmp/bazel_tTNeGhsI/out/external/bazel_tools/WORKSPACE
(@io_bazel) does not match the name given in the repository's definition
(@bazel_tools); this will cause a build error in future versions.
| INFO: Loading package: src
| INFO: Loading package: @bazel_tools//tools/cpp
| INFO: Loading package: @local_config_xcode//
| ERROR: in target '//external:cc_toolchain': no such package
'@local_config_cc//': Traceback (most recent call last):
|       File
"/tmp/bazel_tTNeGhsI/out/external/bazel_tools/tools/cpp/cc_configure.bzl",
line 684
|               _find_cc(repository_ctx)
|       File
"/tmp/bazel_tTNeGhsI/out/external/bazel_tools/tools/cpp/cc_configure.bzl",
line 398, in _find_cc
|               repository_ctx.which(cc_name)
| Program argument of which() may not contains a / or a \
('arm-poky-linux-gnueabi-gcc  -march=armv7-a -marm -mfpu=neon
 -mfloat-abi=hard -mcpu=cortex-a9
--sysroot=/home/giuseppe/research/projects/zynq/yocto/build/tmp/sysroots/zc702-zynq7'
given).
| INFO: Elapsed time: 1.004s
|
| ERROR: Could not build Bazel
| WARNING:
/home/giuseppe/research/projects/zynq/yocto/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/bazel/0.4.5-r0/temp/run.do_compile.4221:1
exit 2 from 'bash ./compile.sh'
| ERROR: Function failed: do_compile (log file is located at
/home/giuseppe/research/projects/zynq/yocto/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/bazel/0.4.5-r0/temp/log.do_compile.4221)
ERROR: Task
(/home/giuseppe/research/projects/zynq/yocto/poky/meta-tensorflow/recipes/bazel/bazel_0.4.5.bb:do_compile)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 1370 tasks of which 1369 didn't need to be
rerun and 1 failed.

Summary: 1 task failed:

/home/giuseppe/research/projects/zynq/yocto/poky/meta-tensorflow/recipes/bazel/bazel_0.4.5.bb:
do_compile
Summary: There was 1 ERROR message shown, returning a non-zero exit code.








On Fri, May 5, 2017 at 1:04 PM, Andrea Galbusera <gizero at gmail.com> wrote:

> On Fri, May 5, 2017 at 4:40 PM, Giuseppe Di Guglielmo <
> giuseppe.diguglielmo at gmail.com> wrote:
>
>> Hi all,
>> I am trying to create a new recipe for Bazel (from Google):
>> https://bazel.build/versions/master/docs/install-compile-source.html
>>
>> The standard compilation flow is relatively simple: "Unzip the archive
>> and call bash ./compile.sh; this will create a bazel binary in
>> output/bazel. This binary is self-contained, so it can be copied to a
>> directory on the PATH (such as /usr/local/bin) or used in-place."
>>
>> I need some support on how to debug the recipe file that I attach.
>>
>> In do_compile(), I run bash ./compile.sh. This requires the JAVA_HOME
>> variable that I export hard-coded because at the moment I do not know how
>> to fetch that path in a recipe. At this point the compile.sh fails and I do
>> not know how to debug. Please, can you have a look at it and provide me
>> some comments?
>>
>
> How does it fail? What is the log from bitbake? Please also provide the
> layers configuration that bitbake shows.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20170505/db024728/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: meta-tensorflow.tgz
Type: application/x-gzip
Size: 1551 bytes
Desc: not available
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20170505/db024728/attachment.bin>


More information about the yocto mailing list