Re: Problem building LizardFS - hidden symbol is referenced by DSO
On Wed, 2017-04-12 at 08:02 +0200, Mattia Verga wrote: > Il 11/04/2017 20:34, Jonathan Dieter ha scritto: > > I would like to get the LizardFS distributed filesystem into > > Fedora, > > but I'm running into problems compiling it with Fedora's hardening > > flags enabled. > > I would greatly appreciate any help pointing me in the right > > direction. > > > > > > You can try to troubleshoot what flag exactly is causing the problem: > https://fedoraproject.org/wiki/Changes/Harden_All_Packages#Troublesho > oting_steps_for_package_maintainers Thanks, this put me on the right track for debugging it > Also, here it is an explanation of the error message: > http://stackoverflow.com/questions/23696585/what-does-exactly-the- > warning-mean-about-hidden-symbol-being-referenced-by-dso And this finally helped me figure out what the problem was. The problem had nothing to do with the hardening flags at all. For each binary, LizardFS normally builds a static library that then gets compiled into the binary. Fedora's default build flags call for dynamic libraries everywhere, but that's what caused the bug I was seeing (and doesn't make much sense anyway, given the context: mfsmetalogger opening the library mfsmetalogger.so to run?) Because LizardFS doesn't actually provide any libraries, I've just passed -DBUILD_SHARED_LIBS:BOOL=OFF and it's fixed. Jonathan ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Problem building LizardFS - hidden symbol is referenced by DSO
Il 11/04/2017 20:34, Jonathan Dieter ha scritto: I would like to get the LizardFS distributed filesystem into Fedora, but I'm running into problems compiling it with Fedora's hardening flags enabled. When the binaries are linked, I get the following error message for each binary: /usr/bin/ld: mfsmetalogger: hidden symbol `__cpu_indicator_init' in /usr/lib/gcc/x86_64-redhat-linux/6.3.1/libgcc.a(cpuinfo.o) is referenced by DSO /usr/bin/ld: final link failed: Bad value collect2: error: ld returned 1 exit status I believe this comes from the file src/common/galois_field_encode.cc where it has different code paths based on the CPU capabilities, but I have no idea why this message is coming up or what the correct way is to fix it. My preliminary SRPM is at https://www.lesbg.com/jdieter/lizardfs-3.10.6 -2.fc25.src.rpm The build log is at https://www.lesbg.com/jdieter/lizardfs-build.log I would greatly appreciate any help pointing me in the right direction. You can try to troubleshoot what flag exactly is causing the problem: https://fedoraproject.org/wiki/Changes/Harden_All_Packages#Troubleshooting_steps_for_package_maintainers Also, here it is an explanation of the error message: http://stackoverflow.com/questions/23696585/what-does-exactly-the-warning-mean-about-hidden-symbol-being-referenced-by-dso I think it would be better to report upstream and ask for a fix. Cheers Mattia ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Problem building LizardFS - hidden symbol is referenced by DSO
I would like to get the LizardFS distributed filesystem into Fedora, but I'm running into problems compiling it with Fedora's hardening flags enabled. When the binaries are linked, I get the following error message for each binary: /usr/bin/ld: mfsmetalogger: hidden symbol `__cpu_indicator_init' in /usr/lib/gcc/x86_64-redhat-linux/6.3.1/libgcc.a(cpuinfo.o) is referenced by DSO /usr/bin/ld: final link failed: Bad value collect2: error: ld returned 1 exit status I believe this comes from the file src/common/galois_field_encode.cc where it has different code paths based on the CPU capabilities, but I have no idea why this message is coming up or what the correct way is to fix it. My preliminary SRPM is at https://www.lesbg.com/jdieter/lizardfs-3.10.6 -2.fc25.src.rpm The build log is at https://www.lesbg.com/jdieter/lizardfs-build.log I would greatly appreciate any help pointing me in the right direction. Thanks, Jonathan ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
