Hi,
I gave a few details on the forum.
repo sync finally succeed, I now try to build the sources.

It failed because some receipt miss:
---
/home/ACCOUNT/ReplicantBuilds-messy-update/replicant-6.0/toolchain/src/binutils/binu
tils-2.25/missing: 81: 
/home/ACCOUNT/ReplicantBuilds-messy-update/replicant-6.0/toolchain/src/binutils/binutils-2.25/missing:
 makeinfo: not found
WARNING: 'makeinfo' is missing on your system.
         You should only need it if you modified a '.texi' file, or
         any other file indirectly affecting the aspect of the manual.
         You might want to install the Texinfo package:
         <http://www.gnu.org/software/texinfo/>
         The spurious makeinfo call might also be the consequence of
         using a buggy 'make' (AIX, DU, IRIX), in which case you might
         want to install GNU make:
         <http://www.gnu.org/software/make/>
Makefile:440 : la recette pour la cible « bfd.info » a échouée
make[3]: *** [bfd.info] Erreur 127
make[3] : on quitte le répertoire « 
/home/ACCOUNT/ReplicantBuilds-messy-update/replicant-6.0/toolchain/gcc/arm/arm-linux-androideabi/build/binutils/bfd/doc
 »
Making info in po
make[3] : on entre dans le répertoire « 
/home/ACCOUNT/ReplicantBuilds-messy-update/replicant-6.0/toolchain/gcc/arm/arm-linux-androideabi/build/binutils/bfd/po
 »
make[3]: rien à faire pour « info ».   
make[3] : on quitte le répertoire « 
/home/ACCOUNT/ReplicantBuilds-messy-update/replicant-6.0/toolchain/gcc/arm/arm-linux-androideabi/build/binutils/bfd/po
 »
make[3] : on entre dans le répertoire « 
/home/ACCOUNT/ReplicantBuilds-messy-update/replicant-6.0/toolchain/gcc/arm/arm-linux-androideabi/build/binutils/bfd
 »
make[3]: rien à faire pour « info-am ».
make[3] : on quitte le répertoire « 
/home/ACCOUNT/ReplicantBuilds-messy-update/repli
cant-6.0/toolchain/gcc/arm/arm-linux-androideabi/build/binutils/bfd »
Makefile:1647 : la recette pour la cible « info-recursive » a échouée
make[2]: *** [info-recursive] Erreur 1 
make[2] : on quitte le répertoire « 
/home/ACCOUNT/ReplicantBuilds-messy-update/repli
cant-6.0/toolchain/gcc/arm/arm-linux-androideabi/build/binutils/bfd »
Makefile:2601 : la recette pour la cible « all-bfd » a échouée
make[1]: *** [all-bfd] Erreur 2
make[1] : on quitte le répertoire « 
/home/ACCOUNT/ReplicantBuilds-messy-update/repli
cant-6.0/toolchain/gcc/arm/arm-linux-androideabi/build/binutils »
Makefile:832 : la recette pour la cible « all » a échouée
make: *** [all] Erreur 2
---
Sorry, for the french locales.
It says info-recursive failed, and it is not present in  
/home/ACCOUNT/ReplicantBuilds-messy-update/replicant-6.0/toolchain/gcc/arm/arm-linux-androideabi/build/binutils/bfd/Makefile
 so I imagine this is the cause.

I'm too exhausted to continue but if anyone has some suggestion, I'd be happy 
to give it a try.

Regards,

- Fil Lupin.

On Monday, June 15th, 2026 at 10:45 PM, Fil Lupin via Replicant 
<[email protected]> wrote:

> 
> Hi Josh,
> I documented the steps I followed in my topic in the forum.
> I made it until repo sync, and I am now stuck at 99% (503/504) 
> platform/system/gatekeeper since 12 hours.
> 
> Any idea how I could go further?
> 
> Regards,
> 
> - Fil Lupin.
> 
> On Friday, June 12th, 2026 at 7:05 AM, Fil Lupin via Replicant 
> <[email protected]> wrote:
> 
> > Hi Josh,
> > thank you for this solution, not sure it will solve the error I documented 
> > on the forum but I'll try asap for sure. :)
> >
> > Regards,
> >
> > - Fil Lupin.
> >
> >
> > On Thursday, June 11th, 2026 at 5:36 PM, J05HYYY via Replicant 
> > <[email protected]> wrote:
> >
> > >
> > > > I am not sure about what I could get from a LXC container since I
> > > > already installed a debian 9. My issue occurs when I tried to follow
> > > > the build process documented on the website, so I do not see
> > > > understand why I should get better results with a container.
> > >
> > > Hi Fil,
> > >
> > > It was a long time ago I compiled Replicant 6 but last time I did, it
> > > required updating the Debian 9 security certificates because the
> > > package is outdated. There are two ways to do this. The first, is using
> > > some kind of container or chroot. The second is copying the updated
> > > certificates using a USB thumb drive.
> > >
> > > Using a container or chroot is easier tbh.
> > >
> > > You can see how to do this by looking at this branch from my repo.
> > >
> > > https://github.com/publicsite/ReplicantBuilds/tree/messy-update-1
> > >
> > > Also have a look at the master branch
> > >
> > > https://github.com/publicsite/ReplicantBuilds/tree/master
> > >
> > > The code will need heavy modification to work however.
> > >
> > > B. Rgs
> > >
> > > Josh
> > > _______________________________________________
> > > Replicant mailing list
> > > [email protected]
> > > https://lists.osuosl.org/mailman/listinfo/replicant
> > >
> > _______________________________________________
> > Replicant mailing list
> > [email protected]
> > https://lists.osuosl.org/mailman/listinfo/replicant
> >
> _______________________________________________
> Replicant mailing list
> [email protected]
> https://lists.osuosl.org/mailman/listinfo/replicant
> 
_______________________________________________
Replicant mailing list
[email protected]
https://lists.osuosl.org/mailman/listinfo/replicant

Reply via email to