32bit and gtk2 builds for Debian/Bookworm

[Paleflo]

is there any chance to see a 32bit gtk2 build for version 34.0.1
https://www.palemoon.org/download.shtml

[Moonchild]

is there any chance to see a 32bit gtk2 build for version 34.0.1
https://www.palemoon.org/download.shtml

We don't offer mainline binaries for 32-bit *nix (and haven't for quite some time).
You can build yourself or maybe there are 3rd party contributed builds that suit your needs.

[andyprough]

is there any chance to see a 32bit gtk2 build for version 34.0.1
https://www.palemoon.org/download.shtml

@wmlive will probably have builds posted soon for you, or if you are in a hurry Veit Kannegieser has builds now: https://kannegieser.net/palemoon/

[Veit Kannegieser]

no, not 32 bits+GTK2, and MX23 does only has 34.0.0 currently.

[wmlive]

is there any chance to see a 32bit gtk2 build for version 34.0.1

Oops, i completely missed the announcements for both 34.0 and 34.0.1...

Give me a few day's time and we will have gtk2 builds for i386, amd64, and arm64 for Debian/Trixie.

[wmlive]

Updated gtk2 based palemoon 34.0.1 debian packages for i386, amd64, and arm64 have been made available here:

wmlive.rumbero.org/repo/pool/main/p/palemoon

The packages using the minor distribution version 0wmlive0 are for bookworm, and those with minor distribution version 0wmlive1 are for trixie.

[printersw5]

Thank you wmlive, it is very useful to have i386 debs.

But the trixie package (palemoon_34.0.1-0wmlive1_i386.deb) still depends on libavcodec 58, 59 or 60 and the trixie repos only have libavcodec61. So I had to add libavcodec61 as an option (58, 69, 60 or 61) in the control file and repackage it to install on trixie.

Would it be possible to add libavcodec61 to the dependencies in future releases?

[wmlive]

@Moonchild:

While building 34.1.0 on the aarch64 variant of Debian/Trixie, compilation fails with an avalanche of build errors.

On both the i386 and amd64 variants of Debian/Trixie, palemoon 34.1.0 builds normally

The full aarch64 build log containing the complete output has been attached:

palemoon-34.1.0_aarch64.buildlog.gz

Any ideas? Or is it only me?

[wmlive]

Would it be possible to add libavcodec61 to the dependencies in future releases?

Thanks for making me aware!
The next builds for Debian/Trixie will have the correct dependencies.

[Moonchild]

compilation fails with an avalanche of build errors.

Well, most of those are informational notices about language standard, but there is one actual error:

Code: Select all

{standard input}: Assembler messages:
{standard input}:5741409: Error: unknown pseudo-op: `.ul' 
g++: fatal error: Terminated signal terminated program cc1plus
compilation terminated. 
make[7]: *** [/srv/wmlive-trixie.d/src/palemoon/palemoon_34.1.0/palemoon-34.1.0/platform/config/rules.mk:879: UnifiedBindings20.o] Error 1

Maybe someone familiar with building on aarch64 can weigh in...
One thing I did notice was you're not building using ./mach build, but rather make -f client.mk build; you may want to use mach instead.

[wmlive]

One thing I did notice was you're not building using ./mach build, but rather make -f client.mk build; you may want to use mach instead.

Interestingly, this alone already made a huge difference and the build finally succeeded also on aarch64.
Thanks a lot for your kind suggestion!

[printersw5]

Thanks for making me aware!
The next builds for Debian/Trixie will have the correct dependencies.

Thank you, wmlive!

[wmlive]

The gtk2 based palemoon 34.1.0 debian packages for i386, amd64, and arm64 have been made available here:

wmlive.rumbero.org/repo/pool/main/p/palemoon

The packages using the minor distribution version 0wmlive0 are for bookworm, and those with minor distribution version 0wmlive1 are for trixie.

Unable to successfully complete a build of the arm64 package on Debian/Bookworm, so the bookworm packages are limited to amd64 and i386 only, while the arm64 package stays at 34.0.1 for the foreseeable future.

The bookworm/arm64 build error is as follows:

Code: Select all

In file included from /mnt/scratch/src/Palemoon/palemoon_34.1.0/palemoon-34.1.0/platform/media/libvpx/libvpx/vp9/encoder/arm/neon/vp9_error_sve.c:17:
/mnt/scratch/src/Palemoon/palemoon_34.1.0/palemoon-34.1.0/platform/media/libvpx/libvpx/vpx_dsp/arm/vpx_neon_sve_bridge.h:16:10: fatal error: arm_neon_sve_bridge.h: No such file or directory
   16 | #include <arm_neon_sve_bridge.h>
      |          ^~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.

There is no package containing arm_neon_sve_bridge.h available on Debian/Bookworm, other than completely unrelated libclang devel packages. Since there doesn't seem to be any way to disable libvpx during build time (it always escaped me why a browser needs to be able to display videos) i just gave up on this target.

[Basilisk-Dev]

There is no package containing arm_neon_sve_bridge.h available on Debian/Bookworm, other than completely unrelated libclang devel packages. Since there doesn't seem to be any way to disable libvpx during build time (it always escaped me why a browser needs to be able to display videos) i just gave up on this target.

You will need to either compile with Clang or apply this patch: https://repo.palemoon.org/MoonchildProd ... pulls/2994