views:

138

answers:

3
A: 

My understanding of the general procedure for building a piece of software packaged using the GNU build system is:

  1. Run the .configure script. This script checks the build environment on your system, ensuring all the required executables, libraries etc are available and creates a working Makefile.
  2. Run make. This uses the Makefile generated in step 1 to build the binary.
  3. Run make install. This installs the binary into the correct location on the system.

GNU Build System

Have you run the .configure script that came with the driver package?

Amal Sirisena
You're thinking of ./configure (ie the name is just configure and the ./ specifies that it's in the current directory, not to be searched in the PATH)
tialaramex
+1  A: 

I think that space in the path to your build directory might be causing the problem.

/home/thayoz/Desktop/untitled folder/Quantis-USB...

Notice the space in 'untitled folder'.

It looks like make is taking the module directory as:

/home/thayoz/Desktop/untitled

And:

folder/Quantis-USB/src/linux/driver

is getting passed to make as an additional argument (probably a target to be built).

Try renaming '/home/thayoz/Desktop/untitled folder' to '/home/thayoz/Desktop/untitledfolder' and see what happens.

Rob Jones
A: 

Typically something like:

make -C <directory to kernel source> M=<directory to module/driver source> modules
make -C <directory to kernel source> M=<directory to module/driver source> modules_install

is sufficient.

Did your driver come with a makefile? Are you compiling against the proper kernel sources, the right version, for instance?

KFro