On Tue, 31 Aug 1999, Richard Spencer wrote:
> I mounted the source CD-ROM and changed to the following directory:
> 
>   cd /cdrom/Redhat/RPMS
> 
> I then did the following:
> rpm -i kernel-headers-2.2.5-15.i386.rpm
> rpm -i kernel-source-2.2.5-15.i386.rpm
>    ( I needed to install the headers package first )
> 
> I then tried make config, make menuconfig and make xconfig, to which I got
> the following message -- without brackets: [bash: make: command not found]
> 
> Advised I would need kernel development rpms loaded, and the
> compiler, I saw rpms in the /cdrom/RedHat/RPMS directory that appeared
> relelvant--because they seemed to be kernel-i386-something or other, so I
> installed those packages as well (...what was I thinking?)
> 
>    The files I unpacked and their [subsequent messages] were:
>    MAKEDEV-2.5-1.noarch.rpm           [package MAKEDEV-2.5-1.noarch.rpm is already 
> installed]
>    kernel-BOOT-2.2.5-15.i386.rpm      [no complaint]
>    kernel-smp-2.2.5-15.i386.rpm       [no complaint]
> 
> 
>    Pleased with trying to install these packages and not getting major
> complaints, I tried the 3 makes again, but the same message still haunts me:
> bash: make: command not found
> 
> I did notice that my /usr/src/linux-2.2.15 directory had contents with today's
> date, and I'm sure I had all the same stuff there before, with a previous
> date. So whatever I've done today so far, I had probably done before.
> 
> It kind of bothers me though, that I don't have a directory for 
> /usr/src/linux -- just the
> link.

Thats the way it should be, you can then have multiple source tree's
all you need to do is remove the symlink from 2.2.5 and make a new
link to say 2.2.10 with;

cd /usr/src
rm linux
ln -s linux-2.2.10 linux

The make command must be issued in the "linux directory.
If that does not work thewn you will need to install the gnu compiler
and development source rpms.



 
> I don't suppose I'm trying to run the bash command 'make' from the wrong
> directory. My bash file is in /bin so that should not make a
> difference. Still, there seems to be trouble with bash, doesn't there?
> 
> Does anyone have an idea about where to go from here?
--
Regards Richard
[EMAIL PROTECTED]

Reply via email to