This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.
Subject: Re: compile kernel: "make modules" reported "nothing to be done?" From: Mark Price <mepr@ilnk.com> Date: Sat, 05 Jun 1999 17:21:54 -0400 Zaigui Wang wrote: > > I compiled my new linux kernel (2.2.9) ok. But when I compiled the sound > modules, I spotted some message like "nothing to be done on modules." This might be a little too simple, but have you tried touch *.c before compiling the sound modules? That usually works for me when I get a message like that. If all the certain if the .o and the .c files or the .o .c and .h files have the same time-stamp, make doesn't know that anything need to be done. === From: "Thomas Ribbrock \(Design/DEG\)" <argathin@iname.com> Date: Wed, 10 Mar 1999 09:44:22 +0000 Subject: Re: Windowmaker src.rpm On Tue, Mar 09, 1999 at 11:51:57PM -0000, Bruce Richardson wrote: [...] > /bin/sh ../mkinstalldirs /var/tmp/WindowMaker-root/usr/share/locale > mkdir /var/tmp/WindowMaker-root/usr/share/locale > chmod 755 /var/tmp/WindowMaker-root/usr/share/locale > for n in __DuMmY ; do \ > if test "$n" -a "$n" != "__DuMmY" ; then \ > l=`basename $n .mo`; \ > /bin/sh ../mkinstalldirs > /var/tmp/WindowMaker-root/usr/share/locale/$l/LC_MESSAGES; \ > chmod 755 /var/tmp/WindowMaker-root/usr/share/locale/$l; \ > chmod 755 /var/tmp/WindowMaker-root/usr/share/locale/$l/LC_MESSAGES; \ > /usr/bin/install -c -m 644 $n > /var/tmp/WindowMaker-root/usr/share/locale/$l/LC_MESSAGES/WindowMaker.mo; \ > fi; \ > done [...] That's a known bug with the Makefile.in in WindowMaker-0.51.0/po. Replace the line nlsdir=$(DESTDIR)/@NLSDIR@ (or similar) with nlsdir=@NLSDIR@ (i.e. the same line without the DESTDIR). BTW: In 0.51.1, the opposite happened - there, you have to add DESTDIR to the targets in po/Makefile and WPrefs/po/Makefile That has already been discussed on the wmaker-devel list. Have a look at the archives at http://www.windowmaker.org/lists.html BTW2: I'm currently working on a 0.51.1 rpm... ;-) === From: Uncle Meat <kcsmart@kcinter.net> Date: Mon, 19 Apr 1999 20:42:00 -0500 (CDT) Subject: RE: Who's the programming guru here? On 20-Apr-99 Rich Shepard opined: > On Mon, 19 Apr 1999, Uncle Meat wrote: > >> It appears the <packagename>-devel-<version>.i386.rpm files aren't >> installed (xxxxx.h is a giveaway). > > I don't understand what you mean. The headers are present. On the > disk. > In /usr/include. The headers may/may not be included in a base package for the operation and minimal compiling. But, the devel packages usually contain additional source, includes, etc. Some programs are written that rely on those additional files. Just because xxxxx.h is there doesn't mean yyyyy.h is also. The first may be a part of the base package, the second being part of the -devel- package. If the program being compiled looks for yyyyy.h and the devel package isn't installed, you get errors. Sometimes this same error is caused by other things: a symlink that should exist but doesn't, a makefile set to look for a file in a specific place when what it needs really exists someplace else (usually written for another distro), other errors that I still am trying to understand (a library that clearly exists in the path where a configure script looks but still can't be found). === From: Michael Elkins <Michael_Elkins@nai.com> Date: Thu, 22 Apr 1999 09:53:39 -0700 Subject: Re: poppassd help On Thu, Apr 22, 1999 at 11:24:45AM -0500, Andres Velez wrote: > [root@alpha poppassd]# make poppassd > cc -o poppassd poppassd.o > poppassd.o: In function `chkPass': > poppassd.c(.text+0x14d0): undefined reference to `crypt' > poppassd.c(.text+0x14d4): undefined reference to `crypt' > collect2: ld returned 1 exit status > make: *** [poppassd] Error 1 Add -lcrypt to the end of your `cc' command. me === From: Godfried Duodu <GDUODU@mailgw.dot.state.tx.us> Date: Fri, 12 Mar 1999 11:22:14 -0600 Subject: Re: Newbie Question ** Reply Requested When Convenient ** I installed RH5.2 obtained from Linuxmall and was trying to recompile the kernel and I kept getting this error message: No rule to make to make target: stop. I was typing 'make mrproper'. Does anyone know what I was doing wrong and how to correct it? Thanks. === From: "Michael R. Steigman" <ms@cs.umb.edu> Date: Fri, 12 Mar 1999 13:27:04 -0500 (EST) Subject: Re: Newbie Question You have to be in the /usr/src/linux directory when you type 'make mrproper'. This assumes that you installed the kernel-source rpm when you installed RH. If you did not install the kernel-source rpm, install it from your CD and then cd to /usr/src/linux and you should be ready to go. === From: John Lewis <jayell@mcmail.com> Date: Thu, 22 Apr 1999 22:59:04 +0100 Subject: Re: Kernel compile question > From: Reverend <statux@bigfoot.com> > To: David Filion <filioda@videotron.com> > CC: redhat-list@redhat.com > > module-info-2.0.34 > > This file isn't honestly needed if you config modules by hand. > > On Thu, 22 Apr 1999, David Filion wrote: > > > I recently tried recompiling my kernel (2.0.34 - yes > > it's old, but it works) and noticed that a file was > > missing. Some kind of module configuration file. > > > > When I installed Linux from the CD I a file named > > modules-???-2.0.34 was installed in the /boot > > directory. (I don't have the exact file name in front of > > me). The file seems to contain a list of modules and > > their configurations. When I compiled my own kernel no > > such file was created. Is this Ok or a problem. > > > This file is hand-written by RedHat and is included with kernel > installation packages. It's used only by kernelcfg (which isn't needed by > the system). kernelcfg writes /etc/conf.modules > On Thu, 22 Apr 1999, Byron Coke wrote: > > I have a couple of questions which I have not been able > > to find an answer for at this time (I've been looking > > for a while) on RedHat Linux ver 5.2 n the /boot > > directory the is a link called 'module-info' pointing to > > a file with the name 'module-info-2.0.36-3'. Does anyone > > know where this file comes from and more pertinent do I > > need to create a different on for a new version of the > > kernel or will the same one work for differing versions > > i.e. could I use this file when booting my machine with > > a 2.2.6 kernel and a 2.0.36 kernel. I subscribed today because I too have had this problem in upgrading from the RedHat 5.2 kernel-2.0.36 to kernel-2.2.2. I was quite surprised to find someone already asking the question I wanted to ask. I went looking for a kernel-2.2.2.rpm in order to get module-info to solve the problem, but there doesn't seem to be any such creature There is a problem in not having the module-info file because it is looked for on boot-up. If by 'config modules by hand' you mean use modprobe, depmod etc, I have tried doing this without any success. Probably because I don't understand the man pages :-)) The whole point of having kerneld is to avoid this. I don't reboot very often but would prefer to have modules loaded automatically when I do. I recompiled a monolithic kernel, so no longer get errors when booting, but ppp gives me error messages every time it is run 'can't locate module ppp-compress-21. 24 and 26'. I seem to remember these are only installable as modules, OK ppp works fine without them but don't want to have to manually load them. So the question is still how can we get a module-info file for later kernels than RedHat provides. Is a new file need for each upgrade? The module-info-2.0.36 file doesn't work with kernel-2.2.2 so will later kernel version (say 2.2.6) work with a module-info-2.2.2 assuming I can get/create one. === From: William Salvino <ws@his.com> Date: Fri, 2 Apr 1999 20:07:55 -0500 (EST) Subject: Custom Kernel Side Effect I recently made a custom kernel so I could try out a commercial sound driver. Prior to this I was successfully using the scripts in /usr/doc/ppp* to connect to my ISP; These are from the stock off the shelf out of the box Official Red Hat Installation cd-rom. I got a bootable custom kernel from which I can connect to the internet but now I can no longer connect to the internet if I boot from my original stock Red Hat 5.2 kernel 2.0.36-0.7. I have tried loading the module with the stock Red Hat kernel but I get the following error message: insmod /lib/modules/2.0.36/net/ppp.o /lib/modules/2.0.36/net/ppp.o: unresolved symbol slhc_free_R3787e5b9 /lib/modules/2.0.36/net/ppp.o: unresolved symbol slhc_remember_Rbc0f8a5e /lib/modules/2.0.36/net/ppp.o: unresolved symbol slhc_toss_R89ec95b6 /lib/modules/2.0.36/net/ppp.o: unresolved symbol slhc_uncompress_Ra2ca7e04 /lib/modules/2.0.36/net/ppp.o: unresolved symbol slhc_compress_R5d6838a9 /lib/modules/2.0.36/net/ppp.o: unresolved symbol slhc_init_R20741a64 Boot installed Red Hat 5.2 kernel 2.0.36-0.7 Log on as root ppp-on from the command line ppp login fails >From /var/log/messages: Apr 1 17:31:29 localhost login[375]: ROOT LOGIN ON tty1 Apr 1 17:31:29 localhost PAM_pwdb[375]: (login) session closed for user root Apr 1 17:31:36 localhost modprobe: no dependency information for module: "/lib /modules/2.0.36/net/ppp.o" Apr 1 17:31:37 localhost modprobe: no dependency information for module: "/lib /modules/2.0.36/net/ppp.o" Apr 1 17:31:37 localhost pppd[394]: ioctl(TIOCSETD): Invalid argument(22) Apr 1 17:31:37 localhost pppd[394]: This system lacks kernel support for PPP. This could be because the PPP kernel module is not loaded, or because the kern el is not configured for PPP. See the README.linux file in the ppp-2.3.5 distr ibution. Boot custom kernel Log on as ws ppp-on from the command line ppp login succeeds >From /var/log/messages: Apr 1 17:38:55 localhost login[393]: LOGIN ON tty1 BY ws Apr 1 17:38:55 localhost PAM_pwdb[393]: (login) session closed for user ws Apr 1 17:38:59 localhost pppd[642]: pppd 2.3.5 started by ws, uid 500 Apr 1 17:39:00 localhost chat[643]: timeout set to 3 seconds ... Apr 1 17:39:29 localhost pppd[642]: Serial connection established. ... Apr 1 17:39:30 localhost pppd[642]: Connect: ppp0 <--> /dev/ttyS1 ... Apr 1 17:39:32 localhost kernel: ppp: channel ppp0 going up for IP packets! Apr 1 17:39:32 localhost pppd[642]: local IP address xxx.xxx.xx.xxx Apr 1 17:39:32 localhost pppd[642]: remote IP address xxx.xxx.xx.xxx I want to connect using either kernel. What do I have to do? Can someone explain what happened when I made a custom kernel: make config, make dep, make clean, make boot, make modules, and make modules_install, and ppp functionality was broken for the original installation kernel. === From: "Jose M. Sanchez" <opjose@ex-pressnet.com> Date: Sat, 3 Apr 1999 01:12:25 -0500 Subject: Re: Custom Kernel Side Effect You did not explicitly follow the directions for the new kernel install. If you are utilizing the same kernel version, you needed to move or delete your OLD kernel modules... You need to perform "make mrproper" "make menuconfig" "make dep" "make clean" "make bzImage" (or zImage if you are lucky) "make modules" "make modules_install "mkinitrd /boot/initrdxxxxx.img 2.x.x" "copy /usr/src/linux/System.map /boot/System-xxxxxx.map" Edit /etc/lilo.conf "lilo" reboot "depmod -a" Then you should be able to reboot without kernel module version errors... Don't specify the full path either, that way you'll pick up the correct kernel modules... thus you should be typing... "/sbin/modprobe ppp" NOT "insmod /lib/modules/2.0.36/net/ppp.o" === From: Statux <statux@bigfoot.com> Date: Thu, 15 Apr 1999 17:46:42 -0400 Subject: Re: kernel 2.2.5 too big says lilo!? Gnana wrote: > I was just upgrading 2.0.36 kernel of Redhat Linux 5.2 to 2.2.5 > I configured kernel with 'make xconfig' and then compiled with 'make > zImage' 'cos compiler repoted the kernel is too big to compile. AS > indicated in README, I then went on to compile 'make bzImage' and I > finally have compiled the kernel. I also compiled modules by 'make > modules' followed by 'make modules_install'. Everything went fine till > here. I have a compiled 'vmlinux' file sized 1.58mb! > > I moved the current kernel to a safe place and copied vmlinux as > vmlinuz-2.2.5 and made the modifications in the /etc/lilo.conf > Then I tried to rerun lilo as indicated in the README, but lilo reports > > "Kernel /boot/vmlinuz-2.2.5 is too big" > > what should i do now? zImage creates /usr/src/linux/arch/i386/boot/zImage zImage is a compressed form of vmlinux. NOTE: vmlinux and vmlinuz are different. copy zImage as stated above to /boot and point vmlinuz to it. also take the System.map from the linux kernel source root directory and copy it to /boot and point System.map to it. also, a cold boot is the best thing to do after a kernel recompile.. I found that out myself.. it gets everything to work like the CDROM drives that often go out afterwards. when you compile a modularized kernel, you should do: # make dep clean modules modules_install zImage install well.. leave off the install if you plan on doing everything yourself (which isn't recommended for some of us) === From: Statux <statux@bigfoot.com> Date: Thu, 15 Apr 1999 17:49:22 -0400 Subject: Re: kernel 2.2.5 too big says lilo!? [2] also.. something I forgot: after you do all that other stuff, do: # depmod -a then make sure you edit your lilo.conf appropriately and make sure your module directory is named correctly and everything's pointing to it and stuff... then run lilo then of course I suggest a cold boot (a reboot has been proven not to reinit stuff properly after a kernel recomp/installation) ===