Dear Erich, thank you very much for your hints. Now I am shure that in my kernel source installation the environment was a little bit confused.
So I installed the original Bering patched kernel source once more, and compiled it with Jaques' original Bering-2.4.20.config. After that I changed the processor type, added the hardware modules I need, and compiled the kernel and the modules. All these compilations were succesful. hfc_pci.c, hfc_pci.h and hfc_pci.o can be found at linux-bering-1.2/drivers/isdn/hisax/ But md5sum complains still, that it cannot open hfc_pci. Evidently there is no file called hfc_pci. md5sum should try to open hfc_pci.h or hfc_pci.c So my questions, maybe a little bit OT: where can I find the call for md5sum, so that I can correct it? why is it called? Thanks again, and regards Thomas * Erich Titl <[EMAIL PROTECTED]> [030925 08:25]: > Thomas > > At 23:01 24.09.2003 +0200, Thomas Wille wrote: > >Erich, > > > >I did all the things I normally do when compiling a new kernel: > >- untar the kernel (in this case into my home dirctory) > >- as root adjust the link /usr/src/linux so that it points to the kernel > > source to be compiled > >- exit from beeing root (in my home directory the user can do everything) > >- edit the config file by menuconfig (in this case I took Jaques' original > > config file) > >- make dep > >- make clean > >- make bzImage > >While doing this step the mentioned error messages occured. > > I see, I just did not grok your statement 'compiling grsecurity'.... > > >but there is another error message in the middle of the compiling process: > >md5sum: kann hfc_pci. nicht öffnen (cannot open hfc_pci.) > >md5sum: kann hfc_pci nicht öffnen (cannot open hfc_pci) > > Looks like it cannot be found in the path. > > > >maybe these error message give a hint to the problem, even if hfc_pci > >belongs to the hisax-module. > > Which IIRC is enabled in the Bering config. > > > >Would it be better to download the original 2.4.20 kernel source and apply > >the patches myself? > > That's what I did. It's worth a try, even with an unpatched kernel source. > That way you can easily verify your environment. > The unpatched kernel source is a good reference point to start from. > > >... > >PS: error messages while making modules: > >make -C maps modules > > You wrote your own makefile, didn't you? > > >make[3]: Entering directory > >/proline/lrp_nfs/Bering1.2/linux-bering-1.2/drivers/mtd/maps' > >gcc -D__KERNEL__ -I/proline/lrp_nfs/Bering1.2/linux-bering-1.2/include > >-Wall > >-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common > >-fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i486 > >-DMODULE > >-nostdinc -iwithprefix include -DKBUILD_BASENAME=dilnetpc -c -o dilnetpc.o > >dilnetpc.c > > Are you trying to cross compile for that hardware? There are probably a few > quirks to the make environment to be done. > > >dilnetpc.c:374: ONFIG_MTD_DILNETPC_BOOTSIZE' undeclared here (not in a > >function) > > Weird, it looks like there is an empty or undefined $C variable. It eats > the uppercase C in the declaration? > > HTH > Erich > > THINK > Püntenstrasse 39 > 8143 Stallikon > mailto:[EMAIL PROTECTED] > PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16 > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
