Linux Format forums

[alloydog]

I have tried on numerous occassions to 'make' a file, but I always get errors.

Here are two examples:

[Gordon]

I presume you mean building a file from source code? These days you don't just "make" a file.

First of all start again. If your source code package is a .tar.gz file (which it seems to be from your code) then unpack it using the command

tar xvzf xxx.tar.gz

where xxx refers to the rest of the filename before the .tar.gz extension. The source code should unpack into its own directory. Use the cd command to change into this new diretory.

Now just list the files in this new directory with the ls command. If you see a README file of any kind then read this first with the command

less README

Do the same thing for any INSTALL files you see in this directory. If there are any special build procedures for the source code then these files should point them out.

If there is a file in this directory you're in called .configure then in due course you will need to run this file, BUT first try the following; run the command,

./configure --help | less

This will output the configuration options for the code to the screen. If you're happy so far then you need to run the following commands from inside the directory containing the source code;

./configure --prefix=/usr
make

and now as root type

make install

All should now be well. There are some older packages of source code out there which use different methods but these days we rarely come across them.

Hope this helps.
Gordon
_________________
Violence is the last refuge of the incompetent

[nelz]

Both of these error indicate you don't have the kernel sources installed. When compiling a driver as a module, the code needs access to the source code for the current kernel. Look for a kernel-source or similarly named package in your distro's package manager.

[Erin]

It seems the second make attempt cannot find the kernel header files. You need to install these from your local install CD or repository. Have the ones for the kernel you are running (check this on the command line by typing 'uname -r' sans quotes. The clue was in "Makefile:4: /usr/src/linux/.config: No such file or directory".

However, you do need to read the README files first. If that doesn't make sense or you need more help, reply.

Erin
_________________
Just beneath my skin I'm screaming. Faithless::Insomnia.
Dual PIII 550 with Ubuntu [semi-bleeding].

[wiz]

From the diff file it looks like this is going to be a kernel module so you will probably need to have the kernel source code installed in /usr/src/linux.

When you have done this once it is easy but can be a bit hairy trying to figure it out for the first time. Check which kernel you are using and then install the source code for it and try again

[wiz]

Hey ! the other two replies sneaked in before mine while i was doing my one finger typing.

[nelz]

Two finger tipping wins again!
_________________
"Insanity: doing the same thing over and over again and expecting different results." (Albert Einstein)

[Erin]

One finger and a rogue cat here!
_________________
Just beneath my skin I'm screaming. Faithless::Insomnia.
Dual PIII 550 with Ubuntu [semi-bleeding].

[alloydog]

Thanks folks, that was wut I wuz needing.

Now to find the kernel source code...

[comcamel]

i get the same problem than that, but after having a look on line, i thought that the problem was that i was using the gcc 4.0 compiler modules, things such as gimp wouldn't compile at all, however thanks for the idea of the kernel sources.