On Sun, Apr 10, 2022 at 3:35 PM stan via kernel <[email protected]> wrote: > > Information. > > I'm building a custom kernel from the src.rpm tuned to my system. The > last 5.17 kernel built just fine. However, this 5.18 kernel fails with > the following error. > > + popd > + pushd tools/arch/x86/intel_sdsi > + /usr/bin/make V=1 'HOSTCFLAGS=-O2 -fexceptions -g -grecord-gcc-switches > -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 > -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 > -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 > -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection > -fcf-protection' 'HOSTLDFLAGS=-Wl,-z,relro -Wl,--as-needed -Wl,-z,now > -specs=/usr/lib/rpm/redhat/redhat-hardened-ld > -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 > -Wl,-dT,/home/stan/rpmbuild/BUILD/kernel-5.18-rc1-184-g1831fed559732b1/.package_note-kernel-5.18.0-0.rc1.20220408git1831fed559732b1.20.20220410.fc37.x86_64.ld' > /usr/bin/ld: /tmp/cc6wxoxI.o: relocation R_X86_64_32 against `.rodata.str1.1' > can not be used when making a PIE object; recompile with -fPIE > /usr/bin/ld: failed to set dynamic section sizes: bad value > collect2: error: ld returned 1 exit status > make: *** [Makefile:13: intel_sdsi] Error 1 > error: Bad exit status from /var/tmp/rpm-tmp.cIdvtt (%build) > Bad exit status from /var/tmp/rpm-tmp.cIdvtt (%build) > > I have the new option CONFIG_X64_X32_ABI disabled, and I am wondering > if it is related to that. I'm not sure why intel_sdsi is even being > processed, since I don't have an intel CPU, and have intel related > CONFIG options disabled in the kernel-local file. Is this an error in > the SPEC file? > > And a note. The rpmbuild -bp kernel.spec command ran without error, > but after I had configured the kernel-local file, and ran > rpmbuild -bb kernel.spec > it complained about a missing package, libnl3-devel. I would have > thought that would be picked up by the -bp command when it expanded the > source. Am I wrong, and this is normal behavior?
I am guessing this is because you turned on a build of kernel-tools with it? libnl3 is only needed for kernel tools (the intel_sdsi build is also kernel-tools only). As to the issues with intel_sdsi, Today would be the first fedora build, so I have not looked at what the issues might be. It looks like it failed Friday for the same reason in the ELN build though. I had not even checked, as the 5.17.2 builds and the 5.16.19 builds and resulting activities kept me busy. Perhaps Prarit might have some insight? Justin _______________________________________________ kernel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
