<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I think the problem I'm seeing isn't kernel related... it's a problem
w/ the build process. It's trying to write to a directory that hasn't
been created yet in the build root.<br>
<br>
The error:<br>
<i>+ modsyms=/var/tmp/OFED_topdir/BUILD/ofa_kernel-1.5/Module.symvers<br>
+ for modsym in '$modsyms'<br>
+ cat /var/tmp/OFED_topdir/BUILD/ofa_kernel-1.5/Module.symvers<br>
/var/tmp/rpm-tmp.91zmLA: line 37:
/var/tmp/OFED_topdir/BUILDROOT/ofa_kernel-1.5-ofed20090922.x86_64//usr/src/ofa_kernel/Module.symvers:
No such file or directory<br>
</i><br>
The script around line 37:<br>
<i>modsyms=`find $RPM_BUILD_DIR/ofa_kernel-1.5 -name Module.symvers -o
-name Modules.symvers`<br>
for modsym in $modsyms<br>
do<br>
cat $modsym >>
$RPM_BUILD_ROOT//usr/src/ofa_kernel/Module.symvers<br>
done<br>
</i><br>
The actual filesystem state:<br>
<i>[root@33 ofa_kernel-1.5-ofed20090922.x86_64]# pwd<br>
/var/tmp/OFED_topdir/BUILDROOT/ofa_kernel-1.5-ofed20090922.x86_64<br>
[root@33 ofa_kernel-1.5-ofed20090922.x86_64]# ls<br>
lib<br>
[root@33 ofa_kernel-1.5-ofed20090922.x86_64]# <br>
</i><br>
Note the lack of a usr folder, hence the error. Isn't anyone else
running into this?<br>
<br>
Jeremy<br>
<br>
Jack Morgenstein wrote:
<blockquote cite="mid:200909131229.29887.jackm@dev.mellanox.co.il"
type="cite">
<pre wrap="">On Thursday 10 September 2009 23:00, Jeremy Enos wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> Fails w/ ofa_kernel like the others have... I didn't test excluding this rpm with FC11, but the others also fail elsewhere w/ this rpm excluded- so I'm guessing FC11 would as well. I included the output (and last 50 lines of log) in case you can glean something useful from it. Thank you-
Jeremy
Build ofa_kernel RPM
Running rpmbuild --rebuild --define '_topdir /var/tmp/OFED_topdir' --define 'configure_options --with-core-mod --with-user_mad-mod --with-user_access-mod --with-addr_trans-mod --with-mthca-mod --with-mlx4-mod --with-mlx4_en-mod --with-cxgb3-mod --with-nes-mod --with-qib-mod --with-ipoib-mod --with-sdp-mod --with-rds-mod --with-qlgc_vnic-mod --with-iser-mod --with-nfsrdma-mod' --define 'build_kernel_ib 1' --define 'build_kernel_ib_devel 1' --define 'KVERSION 2.6.30.5-43.fc11.x86_64' --define 'K_SRC /lib/modules/2.6.30.5-43.fc11.x86_64/build' --define 'network_dir /etc/sysconfig/network-scripts' --define '_prefix /usr' --define '__arch_install_post %{nil}' /home-ib/ac/jenos/ofed/OFED-1.5-beta1/SRPMS/ofa_kernel-1.5-ofed1.5.beta1.src.rpm
Failed to build ofa_kernel RPM
See /tmp/OFED.1584.logs/ofa_kernel.rpmbuild.log
[root@ac32 OFED-1.5-beta1]# tail -50 /tmp/OFED.1584.logs/ofa_kernel.rpmbuild.log
mkdir -p /var/tmp/OFED_topdir/BUILDROOT/ofa_kernel-1.5-ofed1.5.beta1.x86_64//lib/modules/2.6.30.5-43.fc11.x86_64/updates/kernel/net/rds; \
mv /var/tmp/OFED_topdir/BUILD/ofa_kernel-1.5/lib/modules/2.6.30.5-43.fc11.x86_64/extra/net/rds/rds*.ko /var/tmp/OFED_topdir/BUILDROOT/ofa_kernel-1.5-ofed1.5.beta1.x86_64//lib/modules/2.6.30.5-43.fc11.x86_64/updates/kernel/net/rds/ ; \
elif [ -d /var/tmp/OFED_topdir/BUILD/ofa_kernel-1.5/lib/modules/2.6.30.5-43.fc11.x86_64/extra ]; then \
mkdir -p /var/tmp/OFED_topdir/BUILDROOT/ofa_kernel-1.5-ofed1.5.beta1.x86_64//lib/modules/2.6.30.5-43.fc11.x86_64/updates/kernel/net/rds; \
mv /var/tmp/OFED_topdir/BUILD/ofa_kernel-1.5/lib/modules/2.6.30.5-43.fc11.x86_64/extra/rds*.ko /var/tmp/OFED_topdir/BUILDROOT/ofa_kernel-1.5-ofed1.5.beta1.x86_64//lib/modules/2.6.30.5-43.fc11.x86_64/updates/kernel/net/rds/ ; \
fi;
</pre>
</blockquote>
<pre wrap=""><!---->
I notice that you have a 2.6.30-based kernel. The FC11 that we have here is 2.6.29-based:
2.6.29.4-167.fc11.x86_64
Has there been some change in FC11 that we are not aware of?
(the release notes for FC11 also state that it is 2.6.29-based).
That said, I notice that there is a bug in rds on our Fedora Core11 (2.6.29-based).
Andy, you need to put rds_to_2_6_28.patch into a 2.6.29 kernel_patches/backports directory.
There isn't one yet.
I can do this for you, but I suggest a rename to rds_to_2_6_29.patch for the file (in this directory
only).
Summary: I will create kernel_patches/backport/2.6.29 directory, and put rds_to_2_6_29.patch inside.
rds_to_2_6_29.patch is identical to rds_to_2_6_28.patch
NOTE: as of now, there is no need for a separate 2.6.29_FC11 backports directory. If the need
arises, we will create it.
If you ACK, I will take care of it.
-Jack
</pre>
</blockquote>
</body>
</html>