Arch problem in ldtarball
Gary_Lerhaupt at Dell.com
Wed Apr 20 17:20:05 CDT 2005
Great to hear. I'll likely add a fatal error to the mktarball process in the event that the file cannot be found. This should keep this from happening to others.
From: John Lau [mailto:cflau at clustertech.com]
Sent: Tuesday, April 19, 2005 8:05 PM
To: Lerhaupt, Gary - Authorized Dell Representative
Subject: RE: Arch problem in ldtarball
Oh I see. Properly it is because I relocated the path in framework.conf (because my buildroot is read-only and I relocated the path to /var/tmp/dkms-root/ which is set read-write). And the dkms_dbversion is still in the old path and I haven't copy it to the modified path.
I copy it to the new path and the problem fixed. Thank you.
於 二，2005-04-19 於 21:48 -0500，Gary_Lerhaupt at Dell.com 提到：
> Thanks. I noticed the tarball you sent does not contain the file ./dkms_main_tree/dkms_dbversion which is a file that DKMS uses to know whether it’s a 2.0 tarball or not. DKMS gets this file when creating the tarball from /var/lib/dkms/dkms_dbversion and copies it in each time. Can you check and make sure this file did not get deleted on your build machine? It that's the case, perhaps I should probably fail to create tarballs in the event that that file is deleted.
> -----Original Message-----
> From: John Lau [mailto:cflau at clustertech.com]
> Sent: Tuesday, April 19, 2005 7:20 PM
> To: Lerhaupt, Gary - Authorized Dell Representative
> Subject: RE: Arch problem in ldtarball
> This is the offending tarball. Please have a look.
> Best regards,
> John Lau
> 於 二，2005-04-19 於 13:53 -0500，Gary_Lerhaupt at Dell.com 提到：
> > Can you send the offending tarball to my email address?
> > Thanks,
> > Gary
> > -----Original Message-----
> > From: dkms-devel-bounces-Lists On Behalf Of John Lau
> > Sent: Tuesday, April 19, 2005 1:03 AM
> > To: dkms-devel-Lists
> > Subject: Arch problem in ldtarball
> > Hi,
> > I have a problem in using dkms mktarball/ldtarball.
> > When I use ldtarball to deploy a driver tarball that I created on
> > other machine, a warning occurs:
> > Loading/Installing pre-built modules for 2.4.21-15.EL.
> > Warning! This tarball was created with dkms < 2.0 and contains no
> > arch info. DKMS will assume the arch: ia32e
> > But I create the tarball on dkms 2.0.5, with the following command:
> > dkms mktarball -m gm -v 2.0.13 --binaries-only --archive gm-2.0.13-
> > kernel2.4.21-15.EL.tar.gz. I don't know why it said that the tarball
> > was created with dkms < 2.0.
> > After the tarball is installed, I found the binary driver is
> > installed in a wrong path:
> > /var/lib/dkms/gm/2.0.13/2.4.21-15.EL/ia32e/ia32e/module
> > And I can't do a dkms install.
> > Is it a bug in dkms? Or how can I include the missing "arch info"
> > into the tarball? I have tried --arch option but have nothing change.
> > Best regards,
> > John Lau
> > --
> > John Lau Chi Fai
> > Cluster Technology Ltd.
> > cflau at clustertech.com
> > Tel: (852) 2655-6114
> > Fax: (852) 2994-2101
> > _______________________________________________
> > DKMS-devel mailing list
> > DKMS-devel at lists.us.dell.com
> > http://lists.us.dell.com/mailman/listinfo/dkms-devel
> John Lau Chi Fai
> Cluster Technology Ltd.
> cflau at clustertech.com
> Tel: (852) 2655-6114
> Fax: (852) 2994-2101
John Lau Chi Fai
Cluster Technology Ltd.
cflau at clustertech.com
Tel: (852) 2655-6114
Fax: (852) 2994-2101
More information about the DKMS-devel