Open mightyspiky opened 1 year ago
I believe it's still the case that Oracle's distro does things to the package naming and tooling that make it unique compared to other centos/redhat derivatives, and that nobody's written and gotten a fix merged that doesn't require terrible hacks.
Not to say they'd be unwelcome if someone offered them, but I don't know of anyone who regularly writes fixes who runs Oracle UEL.
Good to read you again @rincebrain !! I knew you would be the first to respond to my issue :) . At least, do you think I can be relatively sure I won't get any bad surprise from using my compiled ZFS that has use the mentioned hack (creating symlink gcc-annobin.so pointing at annobin.so) during compilation?
That plugin looks like it's just used to shove extra metadata in the binaries, so I wouldn't inherently expect any excitement about it, but I can't promise anything about a compiler plugin not being exciting.
Just saw this report and wanted to provide a link to the "official" statement from RH:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/developing_c_and_cpp_applications_in_rhel_9/assembly_additional-toolsets-for-development-rhel-9_developing-applications#ref_specifics-of-annobin-in-gcc-toolset-12_gcc-toolset-12
"To work around the problem, create a symbolic link in the plugin directory from the annobin.so file to the gcc-annobin.so file"
System information
Describe the problem you're observing
I get the following error while compiling ZFS 2.1.7 with kernel 5.15.0-6.80.3.1.el8uek.aarch64 from Oracle:
A workaround to make compilation works is to make the following symlink by hand:
After that, compilation works. I just don't know if it's a bug with OpenZFS or with a package from Oracle. Please note that I only have the problem on aarch64, not on x86_64, which I've also tried with same kernel and zfs version.
Describe how to reproduce the problem
Include any warning/errors/backtraces from the system logs