[LU-13315] RHEL8 build failed with some options Created: 02/Mar/20  Updated: 21/May/20  Resolved: 21/May/20

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.14.0
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Alexey Lyashkov Assignee: Alexey Lyashkov
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Related
is related to LU-9897 Tracking of lustre library improvements. Open
is related to LU-13274 Building againt lustreapi using -std=c99 Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

due lack of -fPIC for lnetconfig lib, rhel8 build failed

/usr/bin/ld: ../../lnet/utils/lnetconfig/.libs/liblnetconfig.a(liblnetconfig_la-liblnetconfig.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a PIE object; r
ecompile with -fPIC
/usr/bin/ld: ../../lnet/utils/lnetconfig/.libs/liblnetconfig.a(liblnetconfig_la-liblnetconfig.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a PIE object; r
ecompile with -fPIC
/usr/bin/ld: ../../lnet/utils/lnetconfig/.libs/liblnetconfig.a(liblnetconfig_la-liblnetconfig_lnd.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a PIE objec
t; recompile with -fPIC
/usr/bin/ld: ../../lnet/utils/lnetconfig/.libs/liblnetconfig.a(liblnetconfig_la-liblnetconfig_lnd.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a PIE objec
t; recompile with -fPIC
/usr/bin/ld: ../../lnet/utils/lnetconfig/.libs/liblnetconfig.a(liblnetconfig_la-cyaml.o): relocation R_X86_64_32S against `.rodata' can not be used when making a PIE object; recompile with
-fPIC
/usr/bin/ld: ../../lnet/utils/lnetconfig/.libs/liblnetconfig.a(liblnetconfig_la-cyaml.o): relocation R_X86_64_32S against `.rodata' can not be used when making a PIE object; recompile with
-fPIC
Colla


 Comments   
Comment by James A Simmons [ 18/Mar/20 ]

 I have run into this with my LU-13274 patch - https://review.whamcloud.com/#/c/37971.

Comment by James A Simmons [ 21/May/20 ]

This was fixed with patch https://review.whamcloud.com/#/c/37971/

Generated at Sat Feb 10 03:00:14 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.