From: Tobias Alexandra Platen <guix@platen-software.de>
To: Ian Eure <ian@retrospec.tv>, guix-devel@gnu.org
Subject: Re: guix package -i kicad will fait with #error "Unsupported CPU architecture" on my Talos II
Date: Sun, 01 Dec 2024 12:54:38 +0100 [thread overview]
Message-ID: <bfaad1776c9df951910370585aa25f62af550df8.camel@platen-software.de> (raw)
In-Reply-To: <3ee2fb14-8869-405b-afa1-0280f3ab3ebc@app.fastmail.com>
On Sat, 2024-11-30 at 20:59 +0000, Ian Eure wrote:
> Hi Tobias,
>
> On Sat, Nov 30, 2024, at 8:18 PM, Tobias Alexandra Platen wrote:
> > When I try to install Kicad, I'll get the following output:
> >
> > The following derivations will be built:
> > /gnu/store/5rinv8djwjz0bdami6nr6cm3zj382fsb-libcxi-1.0.1-
> > 0.5b6f8b5.drv
> > /gnu/store/x26zsx3fw74vhfc35i79fansmlmhl0cc-libfabric-1.22.0.drv
> > /gnu/store/nfj2qvhyxvfc7x5fkdlyg2z1wnpqw9cz-openmpi-4.1.6.drv
> > /gnu/store/l1rbmwj9m4kgkm1qada665mm0m6g10w1-libngspice-43.drv
> > /gnu/store/y88c48hzcm78ch39wjfa3dpdgw9n6m7r-webkitgtk-with-
> > libsoup2-
> > 2.44.1.drv
> > /gnu/store/qv0zpz8h2dvhbmxz6smsbmc763rdkdxm-wxwidgets-3.2.5.drv
> > /gnu/store/llydl3baxardzgf9xmdbgjikny68vaar-python-wxpython-
> > 4.2.0.drv
> > /gnu/store/b0s2jgimknw6035kcqvpb6sdxkhakz7b-kicad-7.0.11.drv
> >
> > After a few minutes the build fails with:
> >
> > building /gnu/store/5rinv8djwjz0bdami6nr6cm3zj382fsb-libcxi-1.0.1-
> > 0.5b6f8b5.drv...
> > \ 'build' phasebuilder for
> > `/gnu/store/5rinv8djwjz0bdami6nr6cm3zj382fsb-libcxi-1.0.1-
> > 0.5b6f8b5.drv' failed with exit code 1
> > build of /gnu/store/5rinv8djwjz0bdami6nr6cm3zj382fsb-libcxi-1.0.1-
> > 0.5b6f8b5.drv failed
> > View build log at
> > '/var/log/guix/drvs/5r/inv8djwjz0bdami6nr6cm3zj382fsb-libcxi-1.0.1-
> > 0.5b6f8b5.drv.gz'.
> > ........
> > CC utils/read_lat.o
> > ........
> > #error "Unsupported CPU architecture"
> >
> > I also found a blogpost which mentions libcxi, what does libcxi do?
> > https://hpc.guix.info/blog/2024/11/targeting-the-crayhpe-slingshot-interconnect/
> >
>
> The package description provides a pretty good summary:
>
> Interface to the Cassini/Slingshot high-speed interconnect
>
> Libcxi provides applications with a low-level interface to
> the
> Cray/HPE Cassini high-speed NIC (network interface
> controller), also
> known as Slingshot.
>
> > I guess that libcxi is optional for Kicad, so I could hack guix to
> > build Kicad without libcxi.
Since I do not have that interconnect I would make it optional.
The fastest interconnect that I have is USB 3.0 between my Talos II
(host) and ROCKPro64 (device/otg). I plan to make my own guix channel
anyway with personal changes and for software development. For example
I plan to add guile scripting to eeschema, after I found out that the
python scripts are broken and upgrade to KiCad 8 or any later version.
> >
>
> I think this is worth a bug report, and maybe you're also up to
> sending some patches? I think it's slightly more complicated than
> just the kicad package, though, since libcxi isn't a direct
> dependency:
>
> $ guix graph --path kicad libcxi
> kicad@7.0.11
> libngspice@43
> openmpi@4.1.6
> libfabric@1.22.0
> libcxi@1.0.1-0.5b6f8b5
>
> So, I think what needs to happen is that libcxi needs to have POWER9
> removed from its supported-systems field; and libfabric needs to
> conditionally include libcxi in its inputs based on architecture. I
> think the best way to do that is by checking for the build system in
> (package-supported-systems libcxi), which will avoid hardcoding
> duplicate arch tests in two packages.
>
> -- Ian
>
next prev parent reply other threads:[~2024-12-01 11:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-30 20:18 guix package -i kicad will fait with #error "Unsupported CPU architecture" on my Talos II Tobias Alexandra Platen
2024-11-30 20:59 ` Ian Eure
2024-12-01 11:54 ` Tobias Alexandra Platen [this message]
2024-12-01 13:50 ` Efraim Flashner
2024-12-01 17:51 ` Tobias Alexandra Platen
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bfaad1776c9df951910370585aa25f62af550df8.camel@platen-software.de \
--to=guix@platen-software.de \
--cc=guix-devel@gnu.org \
--cc=ian@retrospec.tv \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).