Deciding that my last little problem probably just came down to the file cache system Linux incorporates, I decided to push on into this brave new world. I also noticed that my regular mag was distributing the new 2.4.19 kernel, so I decided to give that a shot. But there was, you guessed it, a problem. Having logged on as root and copying and decompressing the linux-2.4.19.tar.gz archive in my /usr/src folder, it came time to compile the shiny new code. So, # cd/linux-2.4.19... # make xconfig... # bash: make: command not found. Eh? That can''t be right! # make menuconfig # bash: make: command not found. Huh? But they''re the commands listed on several pages I''ve read on compiling the kernel... but nothing from asking nicely to threatening the little ducky with a mint gravy would get it to compile. How can I talk it around? If at first you don''t succeed, call it version 1.0
SketchSoft | SketchNews

I''ve had a similar problem with make not found. It''s taken for granted that you''ll have a make command on your system, even though many linux distros don''t come with one. You can download it from the linux.org site I think. I''m a linux newbie btw.

quote: Original post by entivore
I''ve had a similar problem with make not found. It''s taken for granted that you''ll have a make command on your system, even though many linux distros don''t come with one. You can download it from the linux.org site I think.

Cheers. I''ll take a look into that!

quote: I''m a linux newbie btw.

If you hadn''t guessed, so am I =P

If at first you don''t succeed, call it version 1.0

SketchSoft | SketchNews

Ok... just for completions sake... after finding linux.org to be about as much use as my rubber ducky, a quick yahoo search revealed that I needed to find a few files called ncurses and ncurses-devel, which I have promptly downloaded and written to my zip disk, ready to take them home and shove them down his little rubb... compile. Cheers, entivore.

If at first you don''t succeed, call it version 1.0

SketchSoft | SketchNews

that wont fix it

in fact you probably already have those

you need make, gcc, & more development tools in order to compile

and somehow I assume make and gcc would be installed together on most distros, so can you compile at all?

quote: Original post by C-Junkie
that wont fix it

in fact you probably already have those

you need make, gcc, & more development tools in order to compile

and somehow I assume make and gcc would be installed together on most distros, so can you compile at all?

Exactly. The problem, doodle_sketch, is that you''re missing the development packages your distro provides (or simply binutils). In the future, you can check for the existence of files (usually executables) in locations on your PATH by typing ''which $filename''.

You''re right, that didn''t fix anything. But only because I can''t decompress the files, I don''t know how to decompress anything through the command line without it being a bz2 file, and these came as straight tar files. I tried using tar filename -extract, but to no avail (thank you tar -help, helpful you bloody were not!).

Anyhow, no I cannot compile the kernel because, as stated above, Mandrake 8.1 (or "Rubber Ducky") dosn''t seem to provide the make command.

If at first you don''t succeed, call it version 1.0

SketchSoft | SketchNews

Debian is a much better distribution, with a far superior packaging system. If you were using Debian, you could just find the names of the packages you need, and then run "apt-get install " to install them.

- Andy Oxfeld

How is apt superior to anything but rpm? If it breaks it has a tendency to completely break, and always in new and fascinating ways... (at least this is my experience with it, it once broke during install for me, there was no way to fix my system other than to install everything again...)

Ports otoh, now there's a sweet system...

/Mikael

[edited by - mikael_j on October 15, 2002 6:41:18 AM]

quote: Original post by doodle_sketch
You''re right, that didn''t fix anything. But only because I can''t decompress the files, I don''t know how to decompress anything through the command line without it being a bz2 file, and these came as straight tar files. I tried using tar filename -extract, but to no avail (thank you tar -help, helpful you bloody were not!).

tar -xvf <filename>