[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-kimageshop
Subject:    Re: Deployment of Meson dependencies
From:       Iván_Yossi <ghevan () gmail ! com>
Date:       2023-02-07 0:41:33
Message-ID: 1da89fd5-3174-4be9-8ee2-5dcb9ce83bfc () Spark
[Download RAW message or body]

I can reproduce it locally, I am not sure why sip is trying to build the =
arm64 version at that point since it fails during the x86=5F64 run, which=
 at that point only x86=5F64 binaries and libraries have been compiled.

Could that be the source of the error=3F

Iv=C3=A1n Yossi
<ghevan=40gmail.com>
IRC: ivanyossi

El 6 de feb de 2023 17:37 -0600, L. E. Segovia <amy=40amyspark.me>, escri=
bi=C3=B3:
> Hi all,
>
> This is to let you know that I've deployed, with almost complete
> success, the dependencies needed for Wolthera and Emmet's branches.
> Android, Windows and Linux are all covered. The only error missing is i=
n
> macOS.
>
> I'm getting assigned the M1 builder and there, PyQt5 fails sip-build
> with the error =22Q=5FPID is not defined=22. All I could find points to=
 a
> missing target flag, which should be of the form =22-t WS=5FMACX=22, an=
d also
> needs the feature =22PyQt=5FProcess=22 defined in QtCoremod.sip to defi=
ne the
> typedef for Q=5FPID. However, for some reason, either that feature or t=
he
> target flag are not detected with the Arm version of Python, and we end=

> up with a failed build.
>
> Iv=C3=A1n, could you try to reproduce it with your machine=3F I believe=
 a
> workaround would be to wait until someone clogs the M1 and we get the
> Intel node, but I'd prefer to see it fixed agnostically...
>
> Cheers,
>
> amyspark
>
> --
> amyspark =F0=9F=8C=B8 https://www.amyspark.me

[Attachment #3 (text/html)]

<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
</head>
<body>
<div name="messageBodySection">
<div dir="auto">I can reproduce it locally, I am not sure why sip is trying to build \
the arm64 version at that point since it fails during the x86_64 run, which at that \
point only x86_64 binaries and libraries have been compiled.<br /> <br />
Could that be the source of the error?</div>
</div>
<div name="messageSignatureSection"><br />
<div class="matchFont">Iván Yossi
<div>&lt;ghevan@gmail.com&gt;</div>
<div>IRC: ivanyossi</div>
<div><br /></div>
</div>
</div>
<div name="messageReplySection">El 6 de feb de 2023 17:37 -0600, L. E. Segovia \
&lt;amy@amyspark.me&gt;, escribió:<br /> <blockquote type="cite" \
style="border-left-color: grey; border-left-width: thin; border-left-style: solid; \
margin: 5px 5px;padding-left: 10px;">Hi all,<br /> <br />
This is to let you know that I've deployed, with almost complete<br />
success, the dependencies needed for Wolthera and Emmet's branches.<br />
Android, Windows and Linux are all covered. The only error missing is in<br />
macOS.<br />
<br />
I'm getting assigned the M1 builder and there, PyQt5 fails sip-build<br />
with the error "Q_PID is not defined". All I could find points to a<br />
missing target flag, which should be of the form "-t WS_MACX", and also<br />
needs the feature "PyQt_Process" defined in QtCoremod.sip to define the<br />
typedef for Q_PID. However, for some reason, either that feature or the<br />
target flag are not detected with the Arm version of Python, and we end<br />
up with a failed build.<br />
<br />
Iván, could you try to reproduce it with your machine? I believe a<br />
workaround would be to wait until someone clogs the M1 and we get the<br />
Intel node, but I'd prefer to see it fixed agnostically...<br />
<br />
Cheers,<br />
<br />
amyspark<br />
<br />
--<br />
amyspark 🌸 https://www.amyspark.me<br /></blockquote>
</div>
</body>
</html>



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic