Gustin Johnson wrote:
>
>> linux-libc-dev and libc6-dev are fighting over installing
>> /usr/include/scsi/scsi.h
>>     
>
> I have build-essential installed on a number of Debian and Ubuntu
> machines as well as my 64Studio machine.  No problems with any of them.
>  My first guess is that there is a 3rd party repository or package that
> is causing you some grief.
>
> You can try to force the install by manually installing the .deb:
> sudo dpkg -i --force-all
> /var/cache/apt/archives/libc6-dev_2.7-10ubuntu5_i386.deb
>
>   
I did this for libc6-dev and linux-libc* and this ended the log jam.
>>   
>>     
>> I typically follow the "building-a-kernel-the-debian-way" articles, but
>> they only add a few other packages. I just don't know if build-essential
>> will straighten-out\add required symlinks etc.
>>
>>     
> "kernel-package" is the easiest way to build a kernel (or a header or
> source) .deb.
>   
kernel-package in now installed, and linux-source-2.6.29, 
build-essential, et al.

1) Do I need apply the patches that came with linux-source, or they 
"pre-applied" and there only if needing to "unroll"?

2) What ".config" file do I use to build the stock 64Studio rt-kernel?

3) How do I stop make-kpkg from asking me all those ".config" questions?

My strategy to address this original problem is to build a new kernel 
(and header files) per the recommendation here:

http://groups.google.co.jp/group/linux.debian.bugs.dist/browse_thread/thread/222248608991112d

Basically they get around this Makefile_32.cpu bug by generating new 
headers from source. If this works, then it seems the 64Studio distro 
could do it and replace the current header file downloads with corrected 
ones?

I could go the patch route, but I don't understand how to apply the 
patch. Do I,

1) cut and paste text sections out of the bug listing and save them to 
xxx.patch files or something?

2) Is there more than one patch (separated by the ######## line)?

The suggestion is to:
"

$ cd /usr/share/kernel-package/ruleset/arches
$ sudo patch -p0 < patch_name
or
$ sudo patch -p1 <  patch_name

"
I dont have a "/usr/share/kernel-package/ruleset/arches" dir... and I 
don't know what "patch_name" refers to.

ANy advice?

Thanks
Rick





_______________________________________________
64studio-users mailing list
[email protected]
http://lists.64studio.com/mailman/listinfo/64studio-users

Reply via email to