Summary: | dev-libs/libgcrypt-1.7.1 installs with TEXTREL on arm | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jaak Ristioja <jaak> |
Component: | Current packages | Assignee: | Crypto team [DISABLED] <crypto+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | k_f, slyfox |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | ARM | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 591534 | ||
Bug Blocks: | |||
Attachments: |
libgcrypt.so.20.1.1
build.log build-.arm.log config.log |
Description
Jaak Ristioja
2016-07-04 19:17:54 UTC
Created attachment 439720 [details]
libgcrypt.so.20.1.1
# scanelf -qT /usr/lib/libgcrypt.so.20.1.1
libgcrypt.so.20.1.1: (memory/data?) [0x5631C] in (optimized out: previous gcry_is_secure) [0xAC64]
/usr/lib/libgcrypt.so.20.1.1
Can you provide configure and build logs? Created attachment 441760 [details]
build.log
/var/tmp/portage/dev-libs/libgcrypt-1.7.1/temp/build.log
Created attachment 441762 [details]
build-.arm.log
/var/tmp/portage/dev-libs/libgcrypt-1.7.1/temp/build-.arm.log
Created attachment 441764 [details]
config.log
/var/tmp/portage/dev-libs/libgcrypt-1.7.1/work/libgcrypt-1.7.1-.arm/config.log
To find where relocation sits you can lookup R_ARM reloc in objdump -R -r: $ armv7a-unknown-linux-gnueabi-objdump -d -r -R -S libgcrypt.so.20.1.1 | grep -C4 R_ARM 56310: e8bd4ff0 pop {r4, r5, r6, r7, r8, r9, sl, fp, lr} 56314: e3a00044 mov r0, #68 ; 0x44 56318: e12fff1e bx lr 5631c: 0005612c andeq r6, r5, ip, lsr #2 5631c: R_ARM_RELATIVE *ABS* 56320: f3870e5f vmov.i8 q0, #255 ; 0xff 56324: f2804011 vmov.i32 d4, #1 ; 0x00000001 56328: f3a00304 vsubw.u32 q0, q0, d4 5632c: ed2d8b10 vpush {d8-d15} $ armv7a-unknown-linux-gnueabi-objdump -d -r -R -S libgcrypt.so.20.1.1 | egrep 'R_ARM|>:' 0000ac64 <gcry_is_secure@@GCRYPT_1.6>: 5631c: R_ARM_RELATIVE *ABS* Building with -ggdb with FEATURES="nostrip" you should be able to find equivalent C (or asm) lines that generate ABS relocs. Does the issue still persist in 1.7.2? Hopefully this was fixed upstream in http://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;a=commit;h=a09126242a51c4ea4564b0f70b808e4f27fe5a91 : Fix non-PIC reference in PIC for poly1305/ARMv7-NEON * cipher/poly1305-armv7-neon.S (GET_DATA_POINTER): New. (_gcry_poly1305_armv7_neon_init_ext): Use GET_DATA_POINTER. (In reply to Kristian Fiskerstrand from comment #7) > Does the issue still persist in 1.7.2? No. The issue does not persist in 1.7.2. (In reply to Jaak Ristioja from comment #8) > (In reply to Kristian Fiskerstrand from comment #7) > > Does the issue still persist in 1.7.2? > > No. The issue does not persist in 1.7.2. ok, setting InVCS keyword until stabilizing 1.7.2 for ARM stabilization happening in 591534 1.7.3 in stable |