Re: Pd-0.56-2 on IRIX
IOhannes m zmoelnig via Pd-list <[email protected]> Wed, 21 Jan 2026 16:15:02 +0100
| Newsgroups | gmane.comp.multimedia.puredata.general |
|---|---|
| Message-ID | <[email protected]> |
On 1/21/26 01:27, Wolfgang Gaggl wrote: > At this point we may just skip the icon all together for Irix. probably you are right. another thing: looking at the screenshot of your system, I noticed that I got a couple of assumptions wrong about your system. e.g. I happily assumed that your system would be somewhat compatible with the old SGI binaries from the beginning of the millenium. iirc, back then we supported "Irix5" (I'm assuming that this was an IRIX-5.x OS) running on o32 mode, and "Irix6" (I guess IRIX-6.x) running in n32 mode. i figure that both were 32-bit systems. now afaict, your system is still an IRIX-6.x, but it's really a 64-bit system, so most likely uses the n64 abi. is this correct? i guess that this should be reflected in the deken architecture. i told you to use "Irix6" and "mips" for deken-os and deken-cpu, but now I think that this is wrong. I guess the proper values should be "Irix" (OS) and "mips64" (CPU) or even "mipsn64". maybe somebody can explain to me how the o32, n32, o64 and n64 ABIs relate to the various OS versions and processors (and then there's all the bi-endianness as well; but i guess IRIX always used big-endian, and little-endian systems usually use the "el" suffix). and which ABI could run on which processor, machine and OS version. e.g. I guess that an "IRIX64" system can run n64 binaries, most likely o64 binaries (is anybody using this?), but maybe also n32 and o32 binaries. "IRIX 6.x" can run n32 and o32 binaries (but probably not the 64bit ABIs). "IRIX 5.x" can run o32 binaries (but not n32). (of course, you cannot use different ABIs in the same process) anyhow, it would be great if you (or really, anybody who still has access to SGI hardware), could run a few tests for me, to see how the various systems can be discovered. esp. i'm interested in - a general system description (e.g. "Octane2, R14000(IP30)") - OS description (e.g. "IRIX64 6.5") - which ABI you are using - the output of `uname` (with as much the information you can get) like `uname -apR` - maybe even the output of `sysconf` - the output of `gcc -dumpmachine` (or similar, depending on the compiler you are using) - maybe even the default preprocessor defines (as reported by `cpp -dM /dev/null`) - the output of the Tcl-command `array get tcl_platform` (you obviously have to run this within "tclsh" resp. "wish" - ideally the Tcl/Tk version that runs Pd) - any other information you can think of :-) mgfadsr IOhannes -- please do not CC me for list-emails --- [email protected] - the Pure Data mailinglist https://lists.iem.at/hyperkitty/list/[email protected]/message/P55W5X2QDB67DP2JF75RE6RQ3O5WWN7A/ To unsubscribe send an email to [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.iem.at/
OpenPGP_signature.asc
(application/pgp-signature, 840 B)
-----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEdAXnRVdICXNIABVttlAZxH96NvgFAmlw7XYFAwAAAAAACgkQtlAZxH96Nvg7 FRAAlQj0L4hmOfbYSm3usXvpH5It/Y1MYD9nGS6mgqwMPH7B40QOlz/MDOnz4VRrkf9fGr4VDuBD Rgn7sf4AeyJFgFd+DoknG1RVVKswHFISyEHMq6XXdmm5C8fdNxYRumr6WzuwiqlWLPc6s1MhTGik RbVaJygG5apE5RbbIinkWuUWIcerRRMy7+AcwmehaU7UhoX/iTWvIGDC95vaTDg25rh3iJIxxWox 9AVSOfIea4zFDV2MVIA/ZeQa/VzQGUOszgIxCu2QuJezSlHA0Xxtcnk1kCJSVniKxnfw+8QtHrI1 n2O7VriPLPK0K6pUXwoNzoFpcDZTYGNot9XT4NvpO2ctol5gOn7pwfJR7jSq727gpZgS4CvHIIeK zT1E2jZstDyhG1Kh3fQFeEsqh2eSDal9beo6K8lcW0xg4fUad1GKXD624jRUZZZh6P4803BiGdTt 8pwYa/DuPsEmzaqMRBxv4IeQ5vSXowvnhX38McE6/5dHa6IdfrTipyJ4BNUsrDRZej+FP+wvfkWw gCydMzAfL+zNUMpsRNMRP4+D5Sp0r5hDhT7U5hOUrfQEzgoEQIGdE4IZ8iviz4wvq34QiexcumJB LLwwyBCOwi9P4ifQt0Ac2xztHhnwctWiFIkCYpGtLU9Uri5vnvzvw3vam3/FWRcaU2TEfr6JJQaC rNs= =hkGP -----END PGP SIGNATURE-----