public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Claudius Heine <claudius.heine.ext@siemens.com>
To: Francesco <fdprnd@dave.eu>, isar-users@googlegroups.com
Subject: Re: Building .deb package from sources fails
Date: Tue, 29 May 2018 14:49:17 +0200	[thread overview]
Message-ID: <00bfa2a3-8ba5-c0ad-d9b1-c801dfb692cb@siemens.com> (raw)
In-Reply-To: <972b546e-0467-53da-658d-21efd95061d3@dave.eu>

Hi Francesco,

On 2018-05-29 14:21, Francesco wrote:
> Hello everyone,
> I'm trying to build the .deb package from the sources of this 
> repository: https://github.com/codeauroraforum/imx-kobs
> This is what I have done looking at your helloworld example:
> 
> recipe imx-kobs_5.5.bb:
> #
> # This software is a part of ISAR.
> # Copyright (C) 2015-2018 ilbers GmbH
> 
> DESCRIPTION = "imx-kobs"
> 
> LICENSE = "gpl-2.0"
> PN = "imx-kobs"
> PV = "5.5"
> 
> SRC_URI = 
> "git://github.com/codeauroraforum/imx-kobs.git;protocol=https;destsuffix=${P}" 
> 
> SRC_URI[md5sum] = "07a9c2114bd73fe3b6491118cbb0eef3"
> SRCREV = "c70685de47cfb67c5e16e1631b7033023ca3e97c"
> inherit dpkg
> 
> 
> When I compile the package using bitbake I'm getting this:
> 
> dave@beleriand /mnt/elbe/Isar/isar/build $ bitbake 
> multiconfig:lynx-config:imx-kobs
> Parsing recipes: 100% 
> |##############################################################################################################################################| 
> Time: 0:00:00Parsing of 9 .bb files complete (0 cached, 9 parsed). 99 
> targets, 0 skipped, 0 masked, 0 errors.
> NOTE: Resolving any missing task queue dependencies
> NOTE: Resolving any missing task queue dependencies
> NOTE: Resolving any missing task queue dependencies
> NOTE: Resolving any missing task queue dependencies
> NOTE: Resolving any missing task queue dependencies
> NOTE: Resolving any missing task queue dependencies
> NOTE: Resolving any missing task queue dependencies
> NOTE: Resolving any missing task queue dependencies
> NOTE: Resolving any missing task queue dependencies
> NOTE: Resolving any missing task queue dependencies
> NOTE: Resolving any missing task queue dependencies
> Initialising tasks: 100% 
> |###########################################################################################################################################| 
> Time: 0:00:00NOTE: Executing RunQueue Tasks
> ERROR: mc:lynx-config:imx-kobs-5.5-r0 do_build: Function failed: 
> do_build (log file is located at 
> /mnt/elbe/Isar/isar/build/tmp/work/lynx-armhf/imx-kobs-5.5-r0/temp/log.do_build.17528) 
> 
> ERROR: Logfile of failure stored in: 
> /mnt/elbe/Isar/isar/build/tmp/work/lynx-armhf/imx-kobs-5.5-r0/temp/log.do_build.17528 
> 
> Log data follows:
> | DEBUG: Executing shell function do_build
> | /build.sh: line 10: cd: 
> /home/builder/imx-kobs//mnt/elbe/Isar/isar/build/tmp/work/lynx-armhf/imx-kobs-5.5-r0/imx-kobs-5.5: 
> No such file or directory
> | WARNING: exit code 1 from a shell command.
> | ERROR: Function failed: do_build (log file is located at 
> /mnt/elbe/Isar/isar/build/tmp/work/lynx-armhf/imx-kobs-5.5-r0/temp/log.do_build.17528) 
> 
> ERROR: Task 
> (multiconfig:lynx-config:/mnt/elbe/Isar/isar/meta-dave/recipes-devtools/kobs-ng/kobs-imx-5.5.bb:do_build) 
> failed with exit code '1'
> NOTE: Tasks Summary: Attempted 11 tasks of which 0 didn't need to be 
> rerun and 1 failed.
> 
> Summary: 1 task failed:
> multiconfig:lynx-config:/mnt/elbe/Isar/isar/meta-dave/recipes-devtools/kobs-ng/kobs-imx-5.5.bb:do_build 
> 
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
> 
> If I look inside the build.sh line 10 is :
> 
>    9 # Go to build directory
>   10 cd $1
> 
> How is $1 passed to the build.sh script from the recipe?
> Why the path is messed up with this prefix : /home/builder/imx-kobs/, 
> when the correct destination is : 
> /mnt/elbe/Isar/isar/build/tmp/work/lynx-armhf/imx-kobs-5.5-r0/imx-kobs-5.5?
> Am I misunderstanding something here?

I don't know what is happening here for you. The 'build.sh' script is 
called by the 'dpkg.bbclass' like this:

     sudo -E chroot ${BUILDCHROOT_DIR} /build.sh ${PP}/${PPS}

You can look at what those variables are by either inspecting the all 
environments "bitbake -e ...| grep -E '^(PP|PPS)'" or looking at the 
generated shell scripts of this task: 
/mnt/elbe/Isar/isar/build/tmp/work/lynx-armhf/imx-kobs-5.5-r0/temp/run.do_build

For me with the example-hello recipe it looks like this:

   PP="/home/builder/example-hello"
   PPS="example-hello-0.2-86cc719"

Good luck,
Claudius

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de

  reply	other threads:[~2018-05-29 12:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-29 12:21 Francesco
2018-05-29 12:49 ` Claudius Heine [this message]
2018-06-05  8:43 ` Henning Schild

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=00bfa2a3-8ba5-c0ad-d9b1-c801dfb692cb@siemens.com \
    --to=claudius.heine.ext@siemens.com \
    --cc=fdprnd@dave.eu \
    --cc=isar-users@googlegroups.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox