Hi Alex,

A simple test case to demonstrate the issue consists in adding libpci-dev 
as a build dependency to example-hello
I have forked and modified hello for this purpose and modifed the recipe as 
follows:

diff --git a/meta-isar/recipes-app/example-hello/example-hello.bb 
b/meta-isar/recipes-app/example-hello/example-hello.bb
index 602a11e..af87428 100644
--- a/meta-isar/recipes-app/example-hello/example-hello.bb
+++ b/meta-isar/recipes-app/example-hello/example-hello.bb
@@ -10,8 +10,8 @@ LIC_FILES_CHKSUM = 
"file://${LAYERDIR_isar}/licenses/COPYING.GPLv2;md5=751419260
 
 PV = "0.2+7bf716d2"
 
-SRC_URI = "git://github.com/ilbers/hello.git;protocol=https"
-SRCREV = "7bf716d22dbdb5a83edf0fe6134c0500f1a8b1f0"
+SRC_URI = "git://github.com/chombourger/hello.git;protocol=https"
+SRCREV = "3f05efe8cd471ce0313b5de6ea992c4a46e0e647"
 
 SRC_DIR = "git"
 
If I bitbake example-hello, do_build will fail. The log will show:

The following NEW packages will be installed:
  libpci-dev libpci3 zlib1g-dev
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 317 kB of archives.
After this operation, 703 kB of additional disk space will be used.
Do you want to continue? [Y/n] Abort.

We get an "Abort" because we do not have a stdin when building from bitbake.

Hope this helps

Cedric

On Monday, January 29, 2018 at 5:15:01 PM UTC+1, Alexander Smirnov wrote:
>
> On 01/29/2018 06:59 PM, Henning Schild wrote: 
> > Am Mon, 29 Jan 2018 16:49:51 +0300 
> > schrieb Alexander Smirnov <asmi...@ilbers.de <javascript:>>: 
> > 
> >> Hello Cedric, 
> >> 
> >> On 01/25/2018 11:36 PM, Cedric_H...@mentor.com <javascript:> wrote: 
> >>> From: Cedric Hombourger <Cedric_H...@mentor.com <javascript:>> 
> >>> 
> >>> commit 498b128 caused build dependencies to be installed via 
> >>> mk-build-deps. 
> >>>> The tool may ask the user to confirm their installation but 
> >>>> would 
> >> fail when 
> >> 
> >> Do you know in which circumstances this could happen? 
> > 
> > Basically whenever apt-get decides to become interactive and wants to 
>
> I do understand what this patch does. My question is exactly when 
> "whenever" really happens. I've noticed such behavior several times for 
> different Debian tools, but it would be nice eventually to understand 
> this kind of magic. 
>
> BTW: for me it's not the point to block this patch. 
>
> Alex 
>
> > ask for confirmation. My patch removed an "apt-get ... -y" while the 
> > "-y" should have stayed. 
> > 
> > Henning 
> > 
> >> Alex 
> >> 
> >>> called from bitbake (no stdin). Override the default install 
> >>> command to add the -y switch (assume yes). 
> >>> 
> >>> Cedric Hombourger (1): 
> >>>     build.sh: eliminate potential prompts from mk-build-deps/apt-get 
> >>> 
> >>>    meta/recipes-devtools/buildchroot/files/build.sh | 5 ++++- 
> >>>    1 file changed, 4 insertions(+), 1 deletion(-) 
> >>>     
> >> 
> > 
>