Hi Jeff： I tried 1.3.17 and it works fine, both making rpm package and installing the rpm package. But the question is our product is validated using 15.6 package. If there is nothing we can do with 1.2.17, it will be a big problem. Or we will have to re-test using 1.3.17. Could you tell us what is the difference between 1.2.17 and 1.3.17 in e1000e.spec? That will help a lot.
Best Regards Miller Liu / 刘建文 EE Server Business, Lenovo E-mail:[email protected] TEL:+86-10-58868956 MP:+86-15801317123 Miller Liu/SBU/LENOVO 2011-06-11 09:00 To [email protected] cc "[email protected]" <[email protected]> Subject Re: [E1000-devel] RHEL Intel NIC Driver RPM Package Issue Hi Jeff: I did some work and found a webpage that may be related with the situation I came across. http://sourceforge.net/tracker/index.php?func=detail&aid=3116036&group_id=42302&atid=447449 And meantime, I will try to use the latest 1.3.17 in package 16.3 to make the rpm again next Monday. I will let you know the result as soon as possible. Thanks very much for your quick response. Best Regards Miller Liu / 刘建文 EE Server Business, Lenovo E-mail:[email protected] TEL:+86-10-58868956 MP:+86-15801317123 Jeff Kirsher <[email protected]> 2011-06-11 06:44 Please respond to [email protected] To Miller Liu <[email protected]> cc "[email protected]" <[email protected]> Subject Re: [E1000-devel] RHEL Intel NIC Driver RPM Package Issue On Fri, 2011-06-10 at 04:05 -0700, Miller Liu wrote: > Hi： > > I'd like to ask for some help. > I was building RPM package under both RHEL 6.0 32bit and 64bit. > But I came across an error. > Please refer to the attachments below. > The tarball was e1000e-1.2.17.tar.gz in package 15.6. > You can find the command I use in the new file.txt. > > Ok well couple of things... First the latest driver released is version 1.3.17 and is available on http://e1000.sourceforge.net In this updated version is also an updated e1000e.spec file which has several cleanups. Although even in the new spec, there is still the section: %install # Append .new to driver name to avoid conflict with kernel RPM cd %{buildroot} find lib -name "e1000e.*o" -exec mv {} {}.new \; \ -fprintf %{_builddir}/%{name}-%{version}/file.list "/%p.new\n" It would be interesting to know if the latest driver (and spec file) worked, or if it has the same error message. Could you please download the latest version and try it?
signature.asc
Description: Binary data
------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________ E1000-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
