Possible issue with the new workflow (i386 architecture)

[ericlyon]

The i386 binaries generated by the new workflow could not load on a couple of Windows computers that we tested. Could someone please look into this? I have confirmed that macOS universal externals work fine on an M1 Mac, after running the following commands:

xattr -r -d com.apple.quarantine .d_fat xattr -r -d com.apple.quarantine .dylib

[Lucarda]

The i386 binaries generated by the new workflow could not load on a couple of Windows computers that we tested. Could someone please look into this?

They work for me. Are you sure you are using the i386 Pd version:

https://msp.ucsd.edu/Software/pd-0.55-1-i386.msw.zip

see pic:

[ericlyon]

Thanks for the update. I'll check on this soon.

[ericlyon]

I was able to get lyonpotpourri working by using the windows-amd64 build, despite the computer being an i386. Maybe because it's a 64-bit rather than 32-bit processor. Deken was not finding the latest build, and it looks like Deken is working differently in your example above, compared with our basic installs of Pd 0.55.1.

[Lucarda]

there might be a misunderstanding.

Windows-amd64 runs i386 stuff but Windows-i386 does not run amd64 stuff. is most unlikely that you will find these days any Windows-i386 machine. i mean any win10 or 11 is running on an amd64 processor on a amd64-OS (that also runs i386 code).

by amd64 i mean an 64bit cpu and by i386 an 32bit cpu.

on a Windows-amd64 and Pd-amd64 you have to run the m_amd64 external

on a Windows-amd64 and Pd-i386 you have to run the m_i386 external

finally on a super edge case:

on a Windows-i386 and Pd-i386 you have to run the m_i386 external

[Lucarda]

I was able to get lyonpotpourri working by using the windows-amd64 build, despite the computer being an i386

this can't happen. an 32bit cpu won't run the "windows-amd64 build" (of Pd or the external)

and it looks like Deken is working differently in your example above, compared with our basic installs of Pd 0.55.1

sound that Pd 0.55.1 is not the i386 one.

[Lucarda]

to summarize you have to run or install the 32bit version of Pd to use m_i386 externals

https://msp.ucsd.edu/software.html

#

[ericlyon]

Thanks for the feedback. I don't own a Windows computer, so I've only been able to spend a few minutes on a school computer, or ask students to check things out. Here's what I think I know:

1) I am running 0.55.1 2) Auto-installing lyonpotpourri from deken finds version 3.0.0, compiled in 2021, which if I understand correctly will no longer run under current Pd builds. This happened for a couple of students who tried deken on their Windows computers. 3) I was very surprised that the amd64 externals loaded but I'm pretty sure that computer shows an Intel processor. I can double check this tomorrow. 4) Manually installing the most recently generated i386 externals did not work on that computer. I'll attach a screenshot from that computer.

I'm unfamiliar with Windows in general, so I appreciate any advice for what to look into here.

[ericlyon]

Following is the deken install window from a student who tried (unsuccessfully) to load lyonpotpourri on his computer.

[ericlyon]

One last thing - I did successfully install the ELSE distribution using deken on the school computer that did not work for lyonpotpourri.

[Lucarda]

ok, i just installed Downloading 'lyonpotpourri[v3.0.0](Windows-amd64-32).dek' from deken and i get into problems with Pd-0.55.1.

show pic

i will investigate and upload the newer builds to deken. I am busy right now for some hours but i hope this is done for tomorrow.

[Lucarda]

ok i uploaded v3.0.2 to deken

https://deken.puredata.info/library/lyonpotpourri/3.0.2

it should be fixed now.

[Lucarda]

@ericlyon one thing for your peace of mind:

the term i386 and amd64 is how GNU Debian distinguishes packages for the 2 most common PC cpu architectures.

i386 is for 32bit cpus (Intel or AMD)

amd64 is for 64bit cpus (Intel or AMD)