FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 05-27-2010, 10:15 AM
Robert Key
 
Default make-kpkg fails writing to weird directories on dual or multi core processors

Hi I have using make-kpkg successfully on my amd64 dual core system
until about a month ago.



I did the following:

installed debian testing amd64

apt-get install kernel-package make g++ gcc build-essentail
libncurses5-dev linux-source-2.6.32



and any other files I needed to build a kernel



I invoked make-kpkg

make-kpkg --initrd --revision custom1.0 --append-to-version custom1.0
kernel_image kernel_headers



( I did not set the CONCURRENCY_LEVEL although I did try it with values
2 and 3 and I still get the same error below)

The compile is fine until the package building starts. Check the errors
below, where does the "-live1.0" come from?

I did not type this in. I have tried uninstalling all the packages and
reinstalling them, using standard kernels to boot from and custom
kernels but nothing works.



However it works fine on my laptop which has a centrino 1.5GHz single
cpu.

I also tried kernel-package version 12.033, 12.032 and the one that
came with lenny. Problem remains the same.



exec make -f /usr/share/kernel-package/ruleset/minimal.mk debian
DEBIAN_REVISION=custom1.0* APPEND_TO_VERSION=custom1.0* V=1* INITRD=YES


====== making target debian/stamp/conf/minimal_debian [new prereqs:
]======

This is kernel package version .

test -d debian************ || mkdir debian

test ! -e stamp-building || rm -f stamp-building

WARNING: Couldn't open directory
/usr/src/linux-source-2.6.26/debian/linux-image-/lib/modules/2.6.32-live1.0:
No
such file or directory

FATAL: Could not open
/usr/src/linux-source-2.6.26/debian/linux-image-/lib/modules/2.6.32-live1.0/modules.dep.temp
for
writing: No such file or directory

make[2]: *** [_modinst_post] Error 1

make[2]: Leaving directory `/mnt/linux/src/linux-source-2.6.26'

make[1]: *** [debian/stamp/install/linux-image-] Error 2

make[1]: Leaving directory `/mnt/linux/src/linux-source-2.6.26'

make: *** [kernel_image] Error 2



Any help would be appreciated.

Thanks,

* Rob Key
 
Old 05-27-2010, 12:29 PM
Robert Key
 
Default make-kpkg fails writing to weird directories on dual or multi core processors

*Hi Here it fails again. this is version 12.033 instead of 12.032

I downloaded kernel--package-12.033.tar.gz



invoke like this

CONCURRENCY_LEVEL=3 make-kpkg --initrd --append-to-version dickhead1.0
kernel_image kernel_headers



All done in /usr/src/linux-source-2.6.32. I am running kernel
vmlinuz-2.6.32-custom1.0



and this is the error



WARNING: Couldn't open directory
/usr/src/linux-source-2.6.32/debian/linux-image-/lib/modules/2.6.32-custom1.0:
No
such file or directory

FATAL: Could not open
/usr/src/linux-source-2.6.32/debian/linux-image-/lib/modules/2.6.32-custom1.0/modules.dep.temp
for
writing: No such file or directory

make[2]: *** [_modinst_post] Error 1

make[2]: Leaving directory `/usr/src/linux-source-2.6.32'

make[1]: *** [debian/stamp/install/linux-image-] Error 2

make[1]: Leaving directory `/usr/src/linux-source-2.6.32'

make: *** [kernel_image] Error 2



Again why is it wanting to write to lib/modules/2.6.32-custom1.0 when
my appendage is dickhead1.0 ?



Some where make-kpkg has done a `uname -r` which would produce*
2.6.32-custom1.0 on my computer?



This is very frustrating. I purged all packages and reinstalled them
all including source.



Please help. thanks,

* Rob Key
 

Thread Tools




All times are GMT. The time now is 08:42 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org