From: "vijaikumar....@gmail.com" <vijaikumar.kanagarajan@gmail.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: pcbios wks files fails for lack of syslinux (#69)
Date: Mon, 20 Sep 2021 20:58:35 -0700 (PDT) [thread overview]
Message-ID: <a292a8fe-4aca-4eec-8f1d-321aa85111d3n@googlegroups.com> (raw)
In-Reply-To: <20210918145155.GX8902@yssyq.m.ilbers.de>
[-- Attachment #1.1: Type: text/plain, Size: 1164 bytes --]
Hi Baurzhan,
Only qemui386 target installs syslinux as wic image depenency.
https://github.com/ilbers/isar/blob/next/meta-isar/conf/machine/qemui386.conf#L9
https://github.com/ilbers/isar/blob/next/meta/conf/distro/debian-common.conf#L26
qemuamd64 uses grub.
https://github.com/ilbers/isar/blob/next/meta-isar/conf/machine/qemuamd64.conf#L11
Thanks,
Vijai Kumar K
On Saturday, September 18, 2021 at 8:22:00 PM UTC+5:30 i...@radix50.net
wrote:
> On Fri, Sep 17, 2021 at 01:39:09PM -0700, Yann Dirson wrote:
> > To get a legacy/pcbios image, I try `WKS_FILE = "directdisk-isar.wks"`
> or `directdisk-gpt.wks` ... which fail looking for syslinux, which is
> apparently not pulled. Some missing dependency ?
> ...
> > Exception: bb.process.ExecutionError: Execution of
> '/home/user/build/tmp/work/debian-buster-amd64/isar-image-base-qemuamd64-wic-img/1.0-r0/temp/run.generate_wic_image.26597'
> failed with exit code 1:
> ...
> > ERROR: Couldn't find syslinux directory, exiting
>
> Do we have a working pcbios example (wic or otherwise)?
>
> I had a short look at xenomai-images and meta-iot2050 but didn't spot one.
>
> With kind regards,
> Baurzhan.
>
[-- Attachment #1.2: Type: text/html, Size: 1568 bytes --]
next prev parent reply other threads:[~2021-09-21 3:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ilbers/isar/issues/69@github.com>
2021-09-18 14:51 ` Baurzhan Ismagulov
2021-09-21 3:58 ` vijaikumar....@gmail.com [this message]
2021-10-21 9:22 ` Baurzhan Ismagulov
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=a292a8fe-4aca-4eec-8f1d-321aa85111d3n@googlegroups.com \
--to=vijaikumar.kanagarajan@gmail.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