> Platform: UnixWare 7.1.4 MP4
> OpenSSL 1.0.2 beta1
> 
> It looks like the latest assembler changes to sha and aes break
> on USL assemblers.
> 
> ----------
> making all in crypto/sha...
>       cc -I.. -I../.. -I../modes -I../asn1 -I../evp -I../../include  
> -DOPENSSL_THREADS -Kthread -DDSO_DLFCN -DHAVE_DLFCN_H -D__i386__ -O -DFILIO_H 
> -Kalloca -DOPENSSL_BN_ASM_PART_WORDS -DOPENSSL_BN_ASM_MONT 
> -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM 
> -DRMD160_ASM -DAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -c -o sha256-586.o 
> sha256-586.s
> UX:as: ERROR: sha256-586.s:28:defined relocatable values from the same 
> section required, op -
> *** Error code 1 (bu21)
> UX:make: ERROR: fatal error.
> ----------

http://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=d00ae7cf7019847c5d35728b01b22461a01bb336

> ----------
> making all in crypto/aes...
>       cc -I.. -I../.. -I../modes -I../asn1 -I../evp -I../../include  
> -DOPENSSL_THREADS -Kthread -DDSO_DLFCN -DHAVE_DLFCN_H -D__i386__ -O -DFILIO_H 
> -Kalloca -DOPENSSL_BN_ASM_PART_WORDS -DOPENSSL_BN_ASM_MONT 
> -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM 
> -DRMD160_ASM -DAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -c -o aes-586.o aes-586.s
> UX:as: ERROR: aes-586.s:1003:defined relocatable values from the same section 
> required, op -
> UX:as: ERROR: aes-586.s:2195:defined relocatable values from the same section 
> required, op -
> UX:as: ERROR: aes-586.s:2251:defined relocatable values from the same section 
> required, op -
> *** Error code 1 (bu21)
> UX:make: ERROR: fatal error.
> ----------

But how did it work in 1.0.0? I mean this is not code that appeared in
1.0.2.

> It does not seem to like lines like
>       leal    OPENSSL_ia32cap_P-.L001K256(%ebp),%edx

Yes, it seems so.


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

Reply via email to