----------
Le 04/02/2024 à 05:49, Alexandre Torres Porres a écrit :
I see, while we're at it, can I ask you to help me compiling just
[plaits~], [circuit~], [sfz~] and [sfont~] for the needed
architectures as soon as I have an official release out in a couple of
days?
Yes, of course.
And out of the 'Linux-arm64-32 / Linux-armv7-32 / Linux-armv6-32',
which one should I not use?
Frankly, I don't know enough about that.
This should be discussed with people understanding how Pd/Deken is
working for determining which RPi OS/HW platform is in use.
What I have done on my RPi 400 regarding myself compiled Pd versions
from 0.53-0 to 0.54-1:
- Pd/Deken installed under RPi OS 11 32-bit
Default platform 'Linux-armv6-32' => User defined-platform
'Linux-arm7-32'
- Pd/Deken installed under RPi OS 12 64-bit (only Pd 0.54-1)
Default platform 'Linux-armv8-32' => User defined-platform
'Linux-arm64-32'
And for your externals I have compiled Else 1.0-0 rc-10, including
the above 4 [*~] objects, from the source code and installed manually
Cyclone from the unzipped 'cyclone-0.8.0_armv8_Linux64.zip'.
- If not and in both OS versions only very few and old externals were
found by Pd/Deken.
thanks
----------
Em sáb., 3 de fev. de 2024 às 16:07, Linux Rouen Normandie
<[email protected]> escreveu:
What I said about 2 months ago is:
- At that time the main used RPi OS was/is v.11 32-bit (based on
Debian Bullseye).
- This OS was/is largely used on all RPi H/W, either 32-bit and/or
64-bit capable.
Since RPi OS 12 64-bit (based on Debian Bookworm) became official
on 11th Oct. 2023
<https://www.raspberrypi.com/news/bookworm-the-new-version-of-raspberry-pi-os/>,
this one will slowly but surely replace RPi OS 11/12 32-bit on the
compatible hardware; i.e. 3B, 3B+, 3A+, 4B, 400, 5, CM3, CM3+,
CM4, CM4S, and Zero 2 W.
My RPi 400 (4 GB RAM) has a chip-set which can run both 32 and
64-bit OSs.
Up to about 2 months ago I was only running under RPi OS 11
32-bit, as recommended by the RPi Foundation (64-bit was not
considered as being enough completed).
Now I'm also running under RPi OS 12 64-bit but this one is still
buggy vs. the previous 32-bit version.
Regarding Pd/Deken (I built it from the source code), I was
obliged for both RPi OS 11 32-bit and RPi OS 12 64-bit to change
the default platform to a user-defined platform to be able to get
access to a larger externals offer.
During my Pd 0.54-1 compilation under RPi OS 12 64-bit I got:
pd 0.54.1 is now configured
Platform: Linux
Float size: default
...
Deken identifier: linux-arm64
...
After my today RPi OS 12 64-bit system update, I have:
OS: Debian GNU/Linux 12 (bookworm) aarch64
Host: Raspberry Pi 400 Rev 1.0
Kernel: 6.1.0-_rpi8_-rpi-v8
-when just few hours ago I had-
OS: Debian GNU/Linux 12 (bookworm) aarch64
Host: Raspberry Pi 400 Rev 1.0
Kernel: 6.1.0-_rpi7_-rpi-v8
-when just after this OS installation I had-
OS: Debian GNU/Linux 12 (bookworm) aarch64
Host: Raspberry Pi 400 Rev 1.0
Kernel: 6.1.0-_rpi6_-rpi-v8
I hope this clarifies a little bit my previous writings. 😉
The Pd/Deken platform detection issue remains open.
- - - - - - - - -
Le 03/02/2024 à 16:18, Alexandre Torres Porres a écrit :
On Sat, 3 Feb 2024 at 09:55 Linux Rouen Normandie
<[email protected]> wrote:
Well - well, who said I have said that !? 😕
I can clearly be wrong with what you said, but then explain again
please :) I just remember something that you mentioned armv8 64
bits is really rare
Now on my RPi 400, I'm running since few weeks the latest RPi
OS 12 64-bit (Debian Bookworm).
At least up to few weeks ago Else was not available for this
platform, except the old v.1.0-0 rc-6.
This why for each release I 'm building Else from its source
code including the missing 4 objects [sfont~], [circuit~],
[sfz~] and [plaits~].
Here my understanding is for seeing the available librairies
in Deken we need to change the Default platform
'Linux-armv8-32' to the User defined-platform 'Linux-arm64-32'.
See the attached screen capture.
But shouldn’t it get it right without this?
Best,
Joseph
----------
Le 03/02/2024 à 07:39, Alexandre Torres Porres a écrit :
Hi, to add on the discussion, Francisco talked to me in
private and I asked him to bring this to the list.
First, I stopped offering raspberry pi binaries for amv8 for
a while now. Joseph (Linux ROUEN Normandie) said that that
it'd be really rare for someone to use it, and Francisco is
using it and needs it, so I'd like to get this straight.
Apparently I should bother and offer these binaries again.
Francisco, do you know why you need this and not something
else? Joseph, can you join in the discussion and tell us
again why this should not be necessary?
Last release I have with 'armv8' binaries is rc6, still up
in deken. Francisco confirmed they work, but it doesn't show
up for him! I am now about to release rc11, and I keep only
the 5 last releases in the serve so I don't take too much
space, so rc6 is about to be deleted. I just uploaded (after
Francisco's email) rc11 binaries for pi (armv6, armv7 and
armv8). It's up in deken... I dont think I need the 3 of
them, but is seems I need at least 2, right?
Now, these uploaded packagee misses 4 objects, [sfont~],
[circuit~], [sfz~] and [plaits~]. I need help compiling them
for armv8 and whatever ELSE I need to provide, so what we
have up there now is just a *test* until we can figure
things out. The dekn system uploaded the packages as
'Linux-arm64-32 / Linux-armv7-32 / Linux-armv6-32'.
Francisco seems to need 'Linux-arm64-32', ('armv8'), and it
doesn't show.
Em sex., 2 de fev. de 2024 às 21:50, Francisco Medeiros
<[email protected]> escreveu:
Deken is not showing the ELSE external, nor many other
externals available for Linux-Arm64-32.
see?
When starting deken says Platform detected:
Linux-aarch64-float32" and "Platform re-detected:
Linux-armv8-float32".
Why both? Now I wonder that maybe it should have detected
'Linux-arm64-32' instead? I don't know...
cheers
_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list
