From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: Harald Seiler <hws@denx.de>, isar-users@googlegroups.com
Subject: Re: DISTRO is set too late
Date: Tue, 23 Oct 2018 12:48:25 +0300 [thread overview]
Message-ID: <485248d7-c66f-8d84-093c-1b74c90dfe8d@ilbers.de> (raw)
In-Reply-To: <56972bf2e66e3d979a1ce1c332594fee59e4ba8f.camel@denx.de>
Hi Harald,
On 10/23/18 12:05 PM, Harald Seiler wrote:
> I am currently porting our layer to `next`. While doing so, I got
> a build failure from c8e63614 (base-apt: Introduce base implementation):
>
> bb.data_smart.ExpansionError: Failure expanding variable DISTRO_SUITE,
> [...] triggered Exception IndexError: list index out of range
>
> The offending line looks like this (base-apt-helper.bbclass):
>
> DISTRO_SUITE ?= "${@ d.getVar('DISTRO', True).split('-')[1]}"
>
> This would work perfectly if $DISTRO was already set to the distro from
> multiconf, but because that seems to happen later on, $DISTRO is still
> `poky` at this point.
> Am I doing something wrong or does this need to be fixed upstream?
The list of supported distros is under isar/meta-isar/conf/distro/*.conf
(debian-wheezy is officially not supported but still present for
convenience).
(see
https://github.com/ilbers/isar/blob/master/doc/user_manual.md#localconf
for more detail)
How did you get the value `poky` for DISTRO in your environment?
Kind regards,
Maxim.
--
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
next prev parent reply other threads:[~2018-10-23 9:48 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 [this message]
2018-10-23 10:10 ` Harald Seiler
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=485248d7-c66f-8d84-093c-1b74c90dfe8d@ilbers.de \
--to=mosipov@ilbers.de \
--cc=hws@denx.de \
--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