public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users <isar-users@googlegroups.com>
Cc: Henning Schild <henning.schild@siemens.com>
Subject: Re: sbuild migration help needed
Date: Fri, 22 Jul 2022 13:20:55 +0300	[thread overview]
Message-ID: <2186291.vFx2qVVIhK@home> (raw)
In-Reply-To: <20220722111635.75271b45@md1za8fc.ad001.siemens.net>

In the email from Friday, 22 July 2022 12:16:35 +03 user Henning Schild wrote:
> Hi,
> 
> i have a recipe where i am building just a util from a bigger package,
> so my S is somewhere inside WORKDIR and some headers are below S.
> 
> With sbuild that recipe stopped working, not finding those headers
> anymore. I did not yet look into the details, but maybe only S get put
> into that chroot and not all of WORKDIR.
> 
> Here is the recipe:
> 
> ifdtool_4.14.bb:

Hello. We could try help with it.

> --
> inherit dpkg
> 
> DESCRIPTION = "Tool for Fast, secure and flexible OpenSource firmware"
> 
> SRC_URI = "https://github.com/coreboot/coreboot/archive/${PV}.tar.gz"
> SRC_URI[sha256sum] =
> "73740c313935f21964577fd6621f9acaddf1244cc704e88046f854d93ed6feab"
> SRC_URI += "file://Makefile-prefix.patch"
> 

Could you also share this patch?

> DEBIAN_DEPENDS = "\${misc:Depends}"
> 
> S = "${WORKDIR}/coreboot-${PV}/util/${PN}"
> 
> do_prepare_build[cleandirs] += "${S}/debian"
> do_prepare_build() {
>         deb_debianize
> }
> --
> 
> Henning


-- 
Uladzimir Bely




  reply	other threads:[~2022-07-22 10:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22  9:16 Henning Schild
2022-07-22 10:20 ` Uladzimir Bely [this message]
2022-07-22 11:11 ` Uladzimir Bely
2022-07-22 13:08   ` Uladzimir Bely
2022-07-22 14:19     ` Henning Schild
2022-07-22 19:16       ` Henning Schild
2022-07-23  6:40         ` Uladzimir Bely
2022-07-25  6:47           ` Moessbauer, Felix

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=2186291.vFx2qVVIhK@home \
    --to=ubely@ilbers.de \
    --cc=henning.schild@siemens.com \
    --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