public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Harald Seiler <hws@denx.de>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>, isar-users@googlegroups.com
Subject: Re: DISTRO is set too late
Date: Tue, 23 Oct 2018 12:10:01 +0200	[thread overview]
Message-ID: <21866f1be8507deb16d968b3d209656327d5eb4c.camel@denx.de> (raw)
In-Reply-To: <485248d7-c66f-8d84-093c-1b74c90dfe8d@ilbers.de>

On Tue, 2018-10-23 at 12:48 +0300, Maxim Yu. Osipov wrote:
> Hi Harald,
> 
> The list of supported distros is under isar/meta-isar/conf/distro/*.conf
> (debian-wheezy is officially not supported but still present for 
> convenience).

We are using `debian-stretch`.  If I add

    DISTRO = "debian-stretch"

to `local.conf`, I can build.  But this should not be necessary as
$DISTRO is also set from multiconf.  The issue is that this happens
too late, so when $DISTRO_SUITE is expanded, it hasn't happened yet.

> How did you get the value `poky` for DISTRO in your environment?

Hmm, apparently this is kas adding

    DISTRO ??= "poky"

to `local.conf` if no distro is supplied in its config.  This should,
again, not be an issue, because the multiconf sets

    DISTRO ?= "debian-stretch"

What seems to go wrong is that the multiconf is read too late, so
that base-apt-helper.bb tries to expand $DISTRO before is has gotten
its final value.  I don't think this is the intended behavior ...

-- 
Harald

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


  reply	other threads:[~2018-10-23 10:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-23  9:05 Harald Seiler
2018-10-23  9:48 ` Maxim Yu. Osipov
2018-10-23 10:10   ` Harald Seiler [this message]
2018-10-23 11:34     ` Maxim Yu. Osipov
2018-10-23 12:37       ` Harald Seiler
2018-10-25 13:21         ` Jan Kiszka
2018-10-30 15:56           ` Harald Seiler

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=21866f1be8507deb16d968b3d209656327d5eb4c.camel@denx.de \
    --to=hws@denx.de \
    --cc=isar-users@googlegroups.com \
    --cc=mosipov@ilbers.de \
    /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