[P4-dev] p4c compilation failed

Andy Fingerhut andy.fingerhut at gmail.com
Fri Feb 7 04:11:35 EST 2020


And in general any of the P4 tool source repositories could change the
commit they use for submodules at arbitrary times during the future, too.
Preferably when building from source, you should use a method to get those
sources that matches the latest submodule commit versions, each time.

Andy

On Fri, Feb 7, 2020 at 12:19 AM Frédéric LOUI <frederic.loui at renater.fr>
wrote:

> Hi Andy, Hemant,
>
> Thanks for your hints.
> Indeed after a quick check, p4c switched:
>
> - from commit [ e7a10bbc4178aad56055ca9384bbdbf18d15341a ]
> - to commit [ a48b45754b39756c226d00380f6e3d00c3087a21 ]
>
> After having changed this, p4c build is successful again.
>
> Merci !
>
> À bientôt,
> --  Frederic
>
>
>
>
> > Le 5 févr. 2020 à 19:01, Andy Fingerhut <andy.fingerhut at gmail.com> a
> écrit :
> >
> > Yes, as Hemant mentioned, probably a submodule issue, like you had for
> PI builds recently.
> >
> > My script that succeeds does this when cloning the p4c source code: `git
> clone --recursive https://github.com/p4lang/p4c.git`
> <https://github.com/p4lang/p4c.git>
> >
> > Probably whatever you did recently to change how the p4lang/PI
> repository is cloned, to get its submodules recursively, would work for p4c
> as well.
> >
> > Andy
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.p4.org/pipermail/p4-dev_lists.p4.org/attachments/20200207/1bfae281/attachment.html>


More information about the P4-dev mailing list