public inbox for developer@lists.illumos.org (since 2011-08)
 help / color / mirror / Atom feed
From: Stephan Althaus <Stephan.Althaus@Duedinghausen.eu>
To: developer@lists.illumos.org, illumos@fiddaman.net
Subject: Re: [developer] Re: illumos/uefi-edk2 update 2023-11
Date: Tue, 13 Feb 2024 13:05:45 +0100	[thread overview]
Message-ID: <7c43f7f5-64d5-4087-b9b6-ccb8f558264b@Duedinghausen.eu> (raw)
In-Reply-To: <17077493090.3fA493c4f.212448@composer.illumos.topicbox.com>

[-- Attachment #1: Type: text/plain, Size: 2084 bytes --]

On 2/12/24 15:48, Andy Fiddaman wrote:
> Last time I tried to build 202311 on illumos it failed due to a number 
> of conflicting type definitions. I haven't had the time to get back to 
> it and see what is going on there.
>
> If you want to try building it yourself then you should be able to 
> just take the upstream tianocore 202311 tag and cherry pick the last 
> three commits from the il-edk2-stable202308, resolving any conflicts, 
> then start from there.
>
> Otherwise I can take a look at the weekend. In the past I've updated 
> this in OmniOS first then pushed the branch to illumos after some 
> period of soak testing.
>
> Andy
> *illumos <https://illumos.topicbox.com/latest>* / illumos-developer / 
> see discussions <https://illumos.topicbox.com/groups/developer> + 
> participants <https://illumos.topicbox.com/groups/developer/members> + 
> delivery options 
> <https://illumos.topicbox.com/groups/developer/subscription> Permalink 
> <https://illumos.topicbox.com/groups/developer/T0e71dad0bc17329a-Mdd0c9611fb1f17d9ee9d9e2a> 
>

Hi Andy!

Thanks for the hint!

Here on OI we lack python >= 3.10 from what i see..

$ pip3 install -r pip-requirements.txt --upgrade
ERROR: Ignored the following versions that require a different python 
version: 0.19.0 Requires-Python >=3.10; 0.19.1 Requires-Python >=3.10; 
0.19.2 Requires-Python >=3.10; 0.19.3 Requires-Python >=3.10; 0.19.4 
Requires-Python >=3.10; 0.19.5 Requires-Python >=3.10; 0.19.6 
Requires-Python >=3.10; 0.19.7 Requires-Python >=3.10; 0.19.8 
Requires-Python >=3.10; 0.19.9 Requires-Python >=3.10; 0.20.0 
Requires-Python >=3.10; 0.21.2 Requires-Python >=3.10; 0.21.3 
Requires-Python >=3.10

.. so i should try to integrate py-312 for OI first ?? i have absolutely 
no idea what has to be done additionally, there are sooo many python 
packages for OI, so this seems out of scope to me right now.


i think i will try to use proxmox first to see if my hardware is able to 
do what i want and then see if i can do it with bhyve..

Thanks!

Stephan


[-- Attachment #2: Type: text/html, Size: 3437 bytes --]

  reply	other threads:[~2024-02-13 12:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-12 12:42 Stephan Althaus
2024-02-12 14:48 ` Andy Fiddaman
2024-02-13 12:05   ` Stephan Althaus [this message]
2024-02-13 12:19     ` [developer] " Marcel Telka
2024-02-16  9:29     ` Stephan Althaus
2024-10-29 15:25       ` Stephan Althaus
2024-10-30  8:32         ` Stephan Althaus
2024-11-28 21:54 ` Andy Fiddaman

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=7c43f7f5-64d5-4087-b9b6-ccb8f558264b@Duedinghausen.eu \
    --to=stephan.althaus@duedinghausen.eu \
    --cc=developer@lists.illumos.org \
    --cc=illumos@fiddaman.net \
    /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;
as well as URLs for NNTP newsgroup(s).