Uploaded image for project: 'Milagro (Retired)'
  1. Milagro (Retired)
  2. MILAGRO-28

config64.py generate compiler errors

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Won't Fix
    • None
    • None
    • Core Crypto Libraries
    • None
    • Ubuntu 18.04 - gcc 7.3

    Description

      The configuration produces compiler errors in the cpp binding. 

      Enviroment: Ubuntu 18.04

      Compiler: gcc (Ubuntu 7.3.0-27ubuntu1~18.04) 7.3.

      Steps to reproduce:

      1. The user launches with python3 configure64.py
      2.  At the screen list start selecting things, in the following way

      Choose a Scheme to support - 0 to finish: 1                
      Choose a Scheme to support - 0 to finish: 2
      ecp_C25519.cpp: In function ‘int C25519::ECP_get(int64_t*, C25519::ECP*)’
      ecp_C25519.cpp:260:14: error: cannot convert ‘C25519::ECP’ to ‘C25519::ECP*’ for argument ‘1’ to ‘void C25519::ECP_affine(C25519::ECP*)’
        ECP_Choose a Scheme to support - 0 to finish: 4Choose a Scheme to support - 0 to finish: 4
      Choose a Scheme to support - 0 to finish: 5
      Choose a Scheme to support - 0 to finish: 6
      Choose a Scheme to support - 0 to finish: 7
      Choose a Scheme to support - 0 to finish: 8
      Choose a Scheme to support - 0 to finish: 9
      Choose a Scheme to support - 0 to finish: 10
      rom_field_NIST521.cpp:26:17: error: ‘B528_56’ is not a namespace-name
      using namespace B528_56;
      ^~~~~~~
      rom_field_NIST521.cpp:26:24: error: expected namespace-name before ‘;’ token
      using namespace B528_56;
      ^
      rom_field_NIST521.cpp:29:7: error: ‘BIG’ does not name a type
      const BIG Modulus= {0xFFFFFFFFFFFFFFFL,0xFFFFFFFFFFFFFFFL,0xFFFFFFFFFFFFFFFL,0xFFFFFFFFFFFFFFFL,0xFFFFFFFFFFFFFFFL,0xFFFFFFFFFFFFFFFL,0xFFFFFFFFFFFFFFFL,0xFFFFFFFFFFFFFFFL,0x1FFFFFFFFFFL};
      ^~~
      rom_field_NIST521.cpp:30:7: error: ‘BIG’ does not name a type
      const BIG R2modp= {0x4000000000L,0x0L,0x0L,0x0L,0x0L,0x0L,0x0L,0x0L,0x0L};
      Choose a Scheme to support - 0 to finish: 5
      Choose a Scheme to support - 0 to finish: 6
      Choose a Scheme to support - 0 to finish: 7
      Choose a Scheme to support - 0 to finish: 8
      Choose a Scheme to support - 0 to finish: 9
      Choose a Scheme to support - 0 to finish: 10
      rom_field_NIST521.cpp:26:17: error: ‘B528_56’ is not a namespace-name
      using namespace B528_56;
      ^~~~~~~
      rom_field_NIST521.cpp:26:24: error: expected namespace-name before ‘;’ token
      using namespace B528_56;
      ^
      rom_field_NIST521.cpp:29:7: error: ‘BIG’ does not name a type
      const BIG Modulus= {0xFFFFFFFFFFFFFFFL,0xFFFFFFFFFFFFFFFL,0xFFFFFFFFFFFFFFFL,0xFFFFFFFFFFFFFFFL,0xFFFFFFFFFFFFFFFL,0xFFFFFFFFFFFFFFFL,0xFFFFFFFFFFFFFFFL,0xFFFFFFFFFFFFFFFL,0x1FFFFFFFFFFL};
      ^~~
      rom_field_NIST521.cpp:30:7: error: ‘BIG’ does not name a type
      const BIG R2modp= {0x4000000000L,0x0L,0x0L,0x0L,0x0L,0x0L,0x0L,0x0L,0x0L};affine(W);

      Suppose now select 0 and exit, we will follow instructions as readme.rst and we have.

      g++ -O2 testall.cpp amcl.a -o testall.exe
      testall.cpp:27:10: fatal error: mpin_BN254.h: No such file or directory
      #include "mpin_BN254.h"

       

       

       

      Attachments

        Activity

          People

            Unassigned Unassigned
            giorgio Giorgio Zoppi
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment