I pulled down the kernel-2.6.18-53.el5.src.rpm source to build my usual custom kernel (adds NTFS wwrite support) and it does not build.* Whether I include the NTFS or just build from the source with no changes (other than make oldconfig and adding the # x86_64 line), I get this error every time:


* Building modules, stage 2.
+ mkdir -p /var/tmp/kernel-2.6.18-53.el5.nx-root/usr/lib/debug/boot
+ mkdir -p /var/tmp/kernel-2.6.18-53.el5.nx-root/usr/lib/debug/boot
+ mkdir -p /var/tmp/kernel-2.6.18-53.el5.nx-root
/boot
+ install -m 644 .config /var/tmp/kernel-2.6.18-53.el5.nx-root/boot/config-2.6.18-53.el5.nx
+ install -m 644 System.map /var/tmp/kernel-2.6.18-53.el5.nx-root/boot/System.map-2.6.18-53.el5.nx
+ touch /var/tmp/kernel-
2.6.18-53.el5.nx-root/boot/initrd-2.6.18-53.el5.nx.img
+ cp arch/x86_64/boot/bzImage /var/tmp/kernel-2.6.18-53.el5.nx-root/boot/vmlinuz-2.6.18-53.el5.nx
+ '[' -f arch/x86_64/boot/zImage.stub ']'
+ '[' ' == kdump ']'

+ mkdir -p /var/tmp/kernel-2.6.18-53.el5.nx-root/lib/modules/2.6.18-53.el5.nx
+ make -s ARCH=x86_64 INSTALL_MOD_PATH=/var/tmp/kernel-2.6.18-53.el5.nx-root modules_install KERNELRELEASE=2.6.18-53.el5.nx
+ echo '**** GENERATING kernel ABI metadata ****'

**** GENERATING kernel ABI metadata ****
+ gzip -c9
+ chmod 0755 /home/rpmbuild/SOURCES/kabitool
+ '[' '!' -e /home/rpmbuild/SOURCES/kabi_whitelist_x86_64 ']'
+ cp /home/rpmbuild/SOURCES/kabi_whitelist_x86_64 /var/tmp/kernel-
2.6.18-53.el5.nx-root/kabi_whitelist
+ rm -f /var/tmp/kernel-2.6.18-53.el5.nx-kabideps
+ /home/rpmbuild/SOURCES/kabitool -b . -d /var/tmp/kernel-2.6.18-53.el5.nx-kabideps -k 2.6.18-53.el5.nx -w /var/tmp/kernel-2.6.18-53.el5.nx-root
/kabi_whitelist
nm: net/decnet/built-in.o: no symbols
nm: net/dccp/ccids/built-in.o: no symbols
nm: net/dccp/built-in.o: no symbols
nm: sound/core/built-in.o: no symbols
nm: drivers/isdn/hardware/built-in.o
: no symbols
nm: drivers/i2c/built-in.o: no symbols
nm: drivers/media/dvb/built-in.o: no symbols
nm: drivers/media/built-in.o: no symbols
nm: drivers/scsi/built-in.o: no symbols
nm: drivers/net/wireless/built-
in.o: no symbols
nm: drivers/message/built-in.o: no symbols
+ echo '**** kABI checking is enabled in kernel SPEC file. ****'
**** kABI checking is enabled in kernel SPEC file. ****
+ chmod 0755 /home/rpmbuild/SOURCES/check-kabi

+ '[' -e /home/rpmbuild/SOURCES/Module.kabi_x86_64 ']'
+ cp /home/rpmbuild/SOURCES/Module.kabi_x86_64 /var/tmp/kernel-2.6.18-53.el5.nx-root/Module.kabi
+ /home/rpmbuild/SOURCES/check-kabi -k /var/tmp/kernel-
2.6.18-53.el5.nx-root/Module.kabi -s Module.symvers
*** ERROR - ABI BREAKAGE WAS DETECTED ***

The following symbols have been changed (this will cause an ABI breakage):

cfi_varsize_frob
unregister_mtd_chip_driver

cfi_read_pri
register_mtd_chip_driver
mtd_do_chip_probe
do_map_probe

+ exit 1
error: Bad exit status from /var/tmp/rpm-tmp.2757 (%build)


RPM build errors:
*** Bad exit status from /var/tmp/rpm-
tmp.2757 (%build)

Should I exclude the kabi (and if so why is it not excluded by default)?* What else did I miss?

Thanks.

mhr

PS: I know I could build that as a module, but that shouldn't make the kernel build fail....



_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

On Dec 3, 2007 9:18 PM, MHR <mhullrich@gmail.com> wrote:

> PS: I know I could build that as a module, but that shouldn't make the
> kernel build fail....

Are you using an otherwise clean build environment? Does rebuilding
the src.rpm (without unpacking, just providing the target) work?


--
During times of universal deceit, telling the truth becomes a revolutionary act.
George Orwell
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos