[openssl.org #2653] [BUG] OpenSSL 1.0.1 OpenVMS issues on VAX

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[openssl.org #2653] [BUG] OpenSSL 1.0.1 OpenVMS issues on VAX

Rich Salz via RT
Hello,

In my earlier mail I have sent a patch that is needed for OpenVMS AXP and IA64.

Here is a list of issues on OpenVMS VAX

1. %CC-E-NOLONGLONG, In this declaration, 64-bit integral types are not supported issue

        cbc128.c
        typedef long long i64;
        ........^
%CC-E-NOLONGLONG, In this declaration, 64-bit integral types are not supported
 on this platform.
                At line number 20 in DKA400:[ZOLI.OPENSSL-101-STABLE-SNAP-20111209.CRYPTO.MODES]MODES_LCL.H;1.

        typedef unsigned long long u64;
        ........^
%CC-E-NOLONGLONG, In this declaration, 64-bit integral types are not supported
 on this platform.
                At line number 21 in DKA400:[ZOLI.OPENSSL-101-STABLE-SNAP-20111209.CRYPTO.MODES]MODES_LCL.H;1.

        }
%VCG-I-NOBJECT, No object file produced.
                At line number 202 in DKA400:[ZOLI.OPENSSL-101-STABLE-SNAP-20111209.CRYPTO.MODES]CBC128.C;1.

%VCG-I-SUMMARY, Completed with 2 error(s), 0 warning(s), and
                1 informational messages.
                At line number 202 in DKA400:[ZOLI.OPENSSL-101-STABLE-SNAP-20111209.CRYPTO.MODES]CBC128.C;1.


This is a general problem and there are many files like: MODES_LCL.H, BN_NIST.C

2. %CC-W-LONGEXTERN, The external identifier name exceeds 31 characters; truncated issue in EC_LCL.H

This is en easy to fix issue - I just wonder why it does not come with IA64 or AXP build

        ec_lib.c
        int ec_GFp_nistp224_point_get_affine_coordinates(const EC_GROUP *group, const EC_POINT *point, BIGNUM *x, BIGNUM *y, BN_CTX *ctx
);
        ....^
%CC-W-LONGEXTERN, The external identifier name exceeds 31 characters; truncated
 to "EC_GFP_NISTP224_POINT_GET_AFFIN".
                At line number 411 in DKA400:[ZOLI.OPENSSL-101-STABLE-SNAP-20111209.CRYPTO.EC]EC_LCL.H;1.

        int ec_GFp_nistp224_have_precompute_mult(const EC_GROUP *group);
        ....^
%CC-W-LONGEXTERN, The external identifier name exceeds 31 characters; truncated
 to "EC_GFP_NISTP224_HAVE_PRECOMPUTE".
                At line number 415 in DKA400:[ZOLI.OPENSSL-101-STABLE-SNAP-20111209.CRYPTO.EC]EC_LCL.H;1.

        int ec_GFp_nistp256_point_get_affine_coordinates(const EC_GROUP *group, const EC_POINT *point, BIGNUM *x, BIGNUM *y, BN_CTX *ctx
);
        ....^
%CC-W-LONGEXTERN, The external identifier name exceeds 31 characters; truncated
 to "EC_GFP_NISTP256_POINT_GET_AFFIN".
                At line number 420 in DKA400:[ZOLI.OPENSSL-101-STABLE-SNAP-20111209.CRYPTO.EC]EC_LCL.H;1.



I think that by solving these issues even on VAX would build correctly.

Thank you.

Regards,
Z




Hello,

 

In my earlier mail I have sent a patch that is needed for OpenVMS AXP and IA64.

 

Here is a list of issues on OpenVMS VAX

 

1. %CC-E-NOLONGLONG, In this declaration, 64-bit integral types are not supported issue

 

        cbc128.c

        typedef long long i64;

        ........^

%CC-E-NOLONGLONG, In this declaration, 64-bit integral types are not supported

 on this platform.

                At line number 20 in DKA400:[ZOLI.OPENSSL-101-STABLE-SNAP-20111209.CRYPTO.MODES]MODES_LCL.H;1.

 

        typedef unsigned long long u64;

        ........^

%CC-E-NOLONGLONG, In this declaration, 64-bit integral types are not supported

 on this platform.

                At line number 21 in DKA400:[ZOLI.OPENSSL-101-STABLE-SNAP-20111209.CRYPTO.MODES]MODES_LCL.H;1.

 

        }

%VCG-I-NOBJECT, No object file produced.

                At line number 202 in DKA400:[ZOLI.OPENSSL-101-STABLE-SNAP-20111209.CRYPTO.MODES]CBC128.C;1.

 

%VCG-I-SUMMARY, Completed with 2 error(s), 0 warning(s), and

                1 informational messages.

                At line number 202 in DKA400:[ZOLI.OPENSSL-101-STABLE-SNAP-20111209.CRYPTO.MODES]CBC128.C;1.

 

 

This is a general problem and there are many files like: MODES_LCL.H, BN_NIST.C

 

2. %CC-W-LONGEXTERN, The external identifier name exceeds 31 characters; truncated issue in EC_LCL.H

 

This is en easy to fix issue – I just wonder why it does not come with IA64 or AXP build

 

        ec_lib.c

        int ec_GFp_nistp224_point_get_affine_coordinates(const EC_GROUP *group, const EC_POINT *point, BIGNUM *x, BIGNUM *y, BN_CTX *ctx

);

        ....^

%CC-W-LONGEXTERN, The external identifier name exceeds 31 characters; truncated

 to "EC_GFP_NISTP224_POINT_GET_AFFIN".

                At line number 411 in DKA400:[ZOLI.OPENSSL-101-STABLE-SNAP-20111209.CRYPTO.EC]EC_LCL.H;1.

 

        int ec_GFp_nistp224_have_precompute_mult(const EC_GROUP *group);

        ....^

%CC-W-LONGEXTERN, The external identifier name exceeds 31 characters; truncated

 to "EC_GFP_NISTP224_HAVE_PRECOMPUTE".

                At line number 415 in DKA400:[ZOLI.OPENSSL-101-STABLE-SNAP-20111209.CRYPTO.EC]EC_LCL.H;1.

 

        int ec_GFp_nistp256_point_get_affine_coordinates(const EC_GROUP *group, const EC_POINT *point, BIGNUM *x, BIGNUM *y, BN_CTX *ctx

);

        ....^

%CC-W-LONGEXTERN, The external identifier name exceeds 31 characters; truncated

 to "EC_GFP_NISTP256_POINT_GET_AFFIN".

                At line number 420 in DKA400:[ZOLI.OPENSSL-101-STABLE-SNAP-20111209.CRYPTO.EC]EC_LCL.H;1.

 

 

 

I think that by solving these issues even on VAX would build correctly.

 

Thank you.

 

Regards,

Z

 
 
Reply | Threaded
Open this post in threaded view
|

Re: [openssl.org #2653] [BUG] OpenSSL 1.0.1 OpenVMS issues on VAX

Rich Salz via RT
> Here is a list of issues on OpenVMS VAX
>
> 1. %CC-E-NOLONGLONG, In this declaration, 64-bit integral types are not supported issue
>
>         cbc128.c
>         typedef long long i64;
>         ........^
> %CC-E-NOLONGLONG, In this declaration, 64-bit integral types are not supported
>  on this platform.
>                 At line number 20 in DKA400:[ZOLI.OPENSSL-101-STABLE-SNAP-20111209.CRYPTO.MODES]MODES_LCL.H;1.

Well, getting rid of 64-bit integer type is labor-intensive and given
the diminishing audience preferred option is to avoid the problem. One
can argue that one can disable modes dependent on 64-bit type the way
one can disable algorithms, but this is also labor-intensive task.
Declaring platforms without 64-bit integer type unsupported is not
unthinkable.

I wonder if VAX gcc supports long long? Do you have one installed? Can
you verify? If it does, what would prevent you from preferring it over
vendor compiler? Otherwise chances are that 1.0.0 would be last one
available for VAX VMS.


______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [hidden email]
Automated List Manager                           [hidden email]