dissapearing kernel-headers
Auke Kok
sofar at lunar-linux.org
Thu May 27 07:12:09 GMT 2004
Richard B. Pyne wrote:
>I still have something screwed up:
>
>.
>.
>.
>Your new glibc installation seems to be ok.
>make[1]: Leaving directory `/usr/src/glibc-2.3.2'
>localedef -i en_US -f ISO-8859-1 en_US
>Creating /var/log/lunar/compile/glibc-2.3.2.bz2
>Creating /var/log/lunar/install/glibc-2.3.2
>Creating /var/log/lunar/md5sum/glibc-2.3.2
>Creating /var/cache/lunar/glibc-2.3.2-i586-pc-linux-gnu.tar.bz2
># lin kernel-headers
>mod_v = mod= kernel-headers
>
>Building kernel-headers
>bzip2: (stdin) is not a bzip2 file.
>tar: Child returned status 2
>tar: Error exit delayed from previous errors
>Creating /var/log/lunar/compile/kernel-headers-Linux-2.4.25-i386.bz2
>! Problem detected during BUILD
># ls /usr/include/linux
>ls: /usr/include/linux: No such file or directory
>
>This poor machine only takes about 8 hours to lin glic.
>
>--Richard
>
>On 27 May 2004 at 0:25, nestu wrote:
>
>
>
>>Richard B. Pyne wrote:
>>
>>
>>>I know this has been covered before, but I can't find it in
>>>either my notes or in the list archives, but what is the
>>>process for re-creating the kernel-headers?
>>>
>>>
>>glibc recreates your headers from /usr/src/linux/
>>
>>
but apparently not if you already have a tarball in /var/spool/lunar.
Even if that one is not a tarball. (hint hint)
try removing the kernel-headers tarball in /var/spool/lunar and rerun
the exercise.
[note: the broken tarball is probably due to the fact that our webserver
was misconfigured and serving broken downloads as a 404.html page
instead, roughly about 10k in size]
sofar
More information about the Lunar
mailing list