Linux: Not able to run on slightly older distributions due to glibc

[probonopd]

The Linux binary currently needs GLIBC_2.43, presumably because it was built on a very new system.

As a result, the binary can't run on, e.g., Devuan Excalibur.

XPCOMGlueLoad error for file /Local/Users/admin/Downloads/arcticfox-47.3.en-US.linux-x86_64/libxul.so:
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.43' not found (required by /Local/Users/admin/Downloads/arcticfox-47.3.en-US.linux-x86_64/libxul.so)
Couldn't load XPCOM.
XPCOMGlueLoad error for file /Local/Users/admin/Downloads/arcticfox-47.3.en-US.linux-x86_64/libxul.so:
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.43' not found (required by /Local/Users/admin/Downloads/arcticfox-47.3.en-US.linux-x86_64/libxul.so)
Couldn't load XPCOM.

Would it be possible to build the binaries on an older system, e.g., Debian oldstable or something like that? This would increase binary compatibility a lot.

Thanks for your consideration!

[rmottola]

@probonopd

I do intel builds on current machines, while more oddball things are for other archs. Binaries are for reference, I hope people build for their own special needs. Build was done on a moderately current gentoo.

What version of glibc do have? please run:
getconf GNU_LIBC_VERSION

I can reproduce your issue try to run my binary on my Devuan laptop, here I have 2.41

If you really need/want I will build you a binary here.

It architecture+library becomes a small maze. I only did an old build for 32bit.

[probonopd]

Thanks for looking into this @rmottola. Maybe it would be worth the effort to build not on your local system, but on a GitHub Actions pipeline? Since you can use Docker there, you can freely decide on which OS to build. Let me know if you would like me to see if I can make a PR.

[rmottola]

@probonopd I built a release for you on 2.41 in the meanwhile, please try. You didn't tell me your glibc version.

We can think of an action for building indeed. Thinks build out of the box, upcoming release removed dependency on autoconf213, but still has python2.7 as a need which is not available in debian and derivates anymore.
I don't know how in actions a dependency could be "stored" so that it does not need to be rebuilt every time. Could be worth trying.