[Bug 217009] [CI] arm64 is failing to link in libpam/modules/pam_krb5: relocation against symbol `__stack_chk_guard@@FBSD_1.0
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sat Feb 11 20:34:46 UTC 2017
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217009
Bug ID: 217009
Summary: [CI] arm64 is failing to link in
libpam/modules/pam_krb5: relocation against symbol
`__stack_chk_guard@@FBSD_1.0
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: misc
Assignee: freebsd-bugs at FreeBSD.org
Reporter: ngie at FreeBSD.org
>From https://ci.freebsd.org/job/FreeBSD-head-arm64-build/531/console :
20:25:09 /usr/local/aarch64-freebsd/bin/ld:
/usr/obj/arm64.aarch64/usr/src/tmp/usr/lib/libkrb5.a(rd_req.o): relocation
R_AARCH64_ADR_PREL_PG_HI21 against external symbol
`__stack_chk_guard@@FBSD_1.0' can not be used when making a shared object;
recompile with -fPIC
20:25:09 /usr/local/aarch64-freebsd/bin/ld:
/usr/obj/arm64.aarch64/usr/src/tmp/usr/lib/libkrb5.a(rd_req.o)(.text+0x4):
unresolvable R_AARCH64_ADR_PREL_PG_HI21 relocation against symbol
`__stack_chk_guard@@FBSD_1.0'
20:25:09 /usr/local/aarch64-freebsd/bin/ld: final link failed: Bad value
20:25:09 cc: error: linker command failed with exit code 1 (use -v to see
invocation)
20:25:09 *** [pam_krb5.so.6.full] Error code 1
20:25:09
20:25:09 make[7]: stopped in /usr/src/lib/libpam/modules/pam_krb5
20:25:09 1 error
20:25:09
20:25:09 make[7]: stopped in /usr/src/lib/libpam/modules/pam_krb5
20:25:09 --- all_subdir_lib/libunbound ---
20:25:09 --- infra.o ---
20:25:09 --- all_subdir_lib/libpam ---
20:25:09 *** [all_subdir_lib/libpam/modules/pam_krb5] Error code 2
20:25:09
20:25:09 make[6]: stopped in /usr/src/lib/libpam/modules
20:25:09 1 error
20:25:09
20:25:09 make[6]: stopped in /usr/src/lib/libpam/modules
20:25:09 *** [all_subdir_lib/libpam/modules] Error code 2
20:25:09
20:25:09 make[5]: stopped in /usr/src/lib/libpam
20:25:09 1 error
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list