Hi Denis, if is consists in building on stretch, I can do this, but I will not have time to make extensives tests on a phone, nor tests with a functionnal SIM. Could it help?
By the way, thank you for the links to commit diff, it will be helpful :) - Fil Lupin. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Tuesday, August 10th, 2021 at 1:25 PM, Denis 'GNUtoo' Carikli via Replicant <[email protected]> wrote: > Hi, > > With the previous serie, we could build the C/C++ toolchain on > > Trisquel 9. This serie fixes the Java toolchain build so with > > both patchsets, we can now build the Replicant 6 toolchain with > > the usual command (./vendor/replicant/build-toolchain). > > I've not yet managed to complete a Replicant 6 build yet with > > Trisquel 9, so it might be a good idea to also test these patches > > on Debian stretch as well. > > There is still some compilation failures to solve when building > > Replicant 6.0 on Trisquel 9. For instance there is a compilation > > error due to with platform/external/libcxx not finding xlocale.h > > that I've already fixed locally, and I've also encountred some > > python errors, so once I've managed to fix them I'll also send > > a new patchset. > > The idea here is to enable to build Replicant 6.0 under at least > > one distribution that follows the Free System Distribution > > Guidelines (FSDG)[1]. > > This is required by the these guidelines. In addition, many people > > wanting to work on Replicant already use distributions that follow > > such guidelines, and there is even some work done (by me and others) > > to enable to easily install an FSDG distribution from another one[2]. > > For instance I use Parabola on the computer that is used to build > > Replicant, but I can very easily create a Trisquel 9 chroot from it > > as the debootstrap pakcage in Parabola has the scripts for Trisquel 9. > > Installing Debian for instance is way more complicated as the Debian > > script has been removed from the Parabola debootstrap as Debian is not > > FSDG compliant[3], and we don't want to force people to use > > distributions that are not FSDG compliant anyway. > > Some of the distributions or distribution versions that follow these > > guidelies[4] are also not packaged in the upstream debootstrap, but > > that could be easily fixed by sending patches to the upstream > > debootstrap for adding support for them. > > References: > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > [1]https://www.gnu.org/distros/free-system-distribution-guidelines.html > > [2]https://libreplanet.org/wiki/Group:Software/research/CrossDistroBootstrap > > [3]https://www.gnu.org/distros/common-distros.html#Debian > > [4]https://www.gnu.org/distros/free-distros.html#for-pc > > How to see the patches in a web or shell interface: > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > In addition to the patch that will follow in a response to > > this mail, here's the URLs to the see the patches in a web interface: > > https://git.replicant.us/contrib/GNUtoo/vendor_replicant/commit/?id=bfe859b89594264b59bdceb3e7cc3b724e68d8f2 > > https://git.replicant.us/contrib/GNUtoo/toolchain_jack/commit/?id=178652c980bc6b0372511a449229cb81e19790bb > > And here's how to get them in a git repository: > > git clone https://git.replicant.us/GNUtoo/vendor_replicant > > cd vendor_replicant > > git show bfe859b89594264b59bdceb3e7cc3b724e68d8f2 > > git show 200b4b0d9c782fe1a0930f3384f675bed06d6c09 > > And for the toolchain_jack patch: > > git clone https://git.replicant.us/GNUtoo/toolchain_jack > > cd toolchain_jack > > git show 178652c980bc6b0372511a449229cb81e19790bb > > Denis. > > Replicant mailing list > > [email protected] > > https://lists.osuosl.org/mailman/listinfo/replicant _______________________________________________ Replicant mailing list [email protected] https://lists.osuosl.org/mailman/listinfo/replicant
