Closed CyrilBrulebois closed 1 year ago
This is the debian/bookworm
branch, with mainly a merge, a new commit entry, and deleted or refreshed patches as needed. The binary package was built in a development environment and not in a clean one just yet. (Building on the first try was unexpected. I guess we'll have more fun later on.)
Same place: frida_16.0.19~pirogue1_arm64.deb
.
Also built in an unclean environment (Pi 4 running Debian 12, where I built many other things lately).
And apparently 68b0826eb3fd6f0a38785f3fb08ccd4439058c21 trivially adds i386
support.
As other packages: built in an unclean, development-oriented environment at the moment.
68b0826..aecd042 HEAD -> debian/bookworm
* [new tag] debian/16.0.19_pirogue1 -> debian/16.0.19_pirogue1
and cleanly-built packages merged into the debian-12
repository.
With our previous/current Debian 11 base, we've had troubles packaging newer upstream releases, and we haven't received any feedback/help from upstream.
With the new/upcoming Debian 12 base, it seems current frida builds fine, at least on amd64.
There are a few steps that are taking a very long time (several minutes on a fast machine), so I'd prefer if @U039b could check whether the
amd64
package is working fine before I try and build anarm64
one.Tentative
frida_16.0.19~pirogue1_amd64.deb
available in our usual Nextcloud space.I'm not sure about
i386
support upstream (didn't check yet), but if there's no upstream toolchain support for it, that might be a blocking point for the whole “PiRogue on i386” scenario. I suppose we should concentrate onamd64
+arm64
first anyway, hence my not looking into it right away.