From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v3 06/16] sdk: Add support for adding self-defined sdk packages
Date: Sun, 1 Nov 2020 16:17:20 +0100 [thread overview]
Message-ID: <20201101151720.GF5078@yssyq.m.ilbers.de> (raw)
In-Reply-To: <03995147-3402-c8dd-47a6-292c64eec70a@siemens.com>
On Fri, Oct 16, 2020 at 09:15:12AM +0200, Jan Kiszka wrote:
> Checking... Nope, works fine here:
>
> - echo 'SDK_INCLUDE_ISAR_APT = "1"' >> conf/local.conf
> - bitbake -c populate_sdk mc:qemuarm-buster:isar-image-base
> - sudo tar xJf
> /work/build/tmp/deploy/images/qemuarm/sdk-debian-buster-armhf.tar.xz
> - sudo sdk-debian-buster-armhf/mount_chroot.sh sdk-debian-buster-armhf/
> - sudo chroot sdk-debian-buster-armhf/
>
> root@566b0c868313:/# arm-linux-gnueabihf-gcc
> arm-linux-gnueabihf-gcc-8.bin: fatal error: no input files
> compilation terminated.
Thanks for the details! Turns out I made a mistake while applying the series.
> No, that section will not stay for the common case. I will add the
> relevant parts in case SDK_INCLUDE_ISAR_APT = 1 and still drop the
> irrelevant ones (toolchain check).
As discussed offline, I'd like to have a consensus here. To summarize, your
point is that the description is not necessary if README.sdk is used as a
literal howto, and that the deeper message is only clear for expert users, who
know that anyway. Given these questions, I agree with the answers. My question
is a different one: Multiarch is Debian's unique feature for embedded
development, and we should be covering that somewhere in the docs. As a
solution, I'd like to enhance the existing docs instead of removing them. I've
checked the user manual, the topics are covered there. I've applied v4. As
agreed, the enhancements can still be implemented, I can provide them on top.
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2020-11-01 15:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 15:28 [PATCH v3 00/16] Complete backlog: SDK, compat arch, assorting fixed and cleanups Jan Kiszka
2020-09-22 15:28 ` [PATCH v3 01/16] Split up isar-apt into distro-arch specific instances Jan Kiszka
2020-10-06 8:29 ` Baurzhan Ismagulov
2020-09-22 15:28 ` [PATCH v3 02/16] linux-custom: Clean up minor inconsistencies in rules.tmpl Jan Kiszka
2020-09-22 15:28 ` [PATCH v3 03/16] sshd-regen-keys: Issue sync after regeneration Jan Kiszka
2020-09-22 15:28 ` [PATCH v3 04/16] meta-isar: Drop outdated cross-compilation comment Jan Kiszka
2020-09-22 15:28 ` [PATCH v3 05/16] qemuamd64: Fix OVMF path Jan Kiszka
2020-09-22 15:28 ` [PATCH v3 06/16] sdk: Add support for adding self-defined sdk packages Jan Kiszka
2020-09-29 19:15 ` Baurzhan Ismagulov
2020-09-30 19:19 ` Jan Kiszka
2020-10-06 9:00 ` Baurzhan Ismagulov
2020-10-07 7:30 ` Jan Kiszka
2020-10-07 8:06 ` Baurzhan Ismagulov
2020-10-07 13:36 ` Jan Kiszka
2020-10-15 21:51 ` Baurzhan Ismagulov
2020-10-16 7:15 ` Jan Kiszka
2020-11-01 15:17 ` Baurzhan Ismagulov [this message]
2020-09-22 15:28 ` [PATCH v3 07/16] sdk: Make all links in the SDK chroot relative Jan Kiszka
2020-09-22 15:28 ` [PATCH v3 08/16] sdk: Add script to relocate SDK Jan Kiszka
2020-09-22 15:28 ` [PATCH v3 09/16] sdk: Make shipping the isar-apt repo opt-in Jan Kiszka
2020-09-22 15:28 ` [PATCH v3 10/16] sdk: Inject sysroot path when calling relocated toolchain Jan Kiszka
2020-09-22 15:28 ` [PATCH v3 11/16] sdk: Update README.sdk Jan Kiszka
2020-09-22 15:28 ` [PATCH v3 12/16] Add compat architecture support via multiarch Jan Kiszka
2020-09-24 20:19 ` Baurzhan Ismagulov
2020-09-22 15:28 ` [PATCH v3 13/16] ci: Add compat arch support Jan Kiszka
2020-09-22 15:28 ` [PATCH v3 14/16] doc: Enhance list of supported cross-archs, drop QEMU reference Jan Kiszka
2020-09-22 15:28 ` [PATCH v3 15/16] doc: Describe new compat arch support Jan Kiszka
2020-09-22 15:28 ` [PATCH v3 16/16] isar-bootstrap: Connect to gpg-agent before adding keys Jan Kiszka
2020-09-22 21:03 ` Jan Kiszka
2020-09-23 20:29 ` Baurzhan Ismagulov
2020-09-24 9:10 ` [PATCH v4 " Jan Kiszka
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=20201101151720.GF5078@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--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