Find the answer to your Linux question:
Results 1 to 4 of 4
I downloaded a linux driver for a PCI card peripheral and did an initial 'make' and got errors. The main directory makefile goes through 3 subdirectories to make each of ...
  1. #1
    Just Joined!
    Join Date
    Nov 2007
    Posts
    8

    Makefile errors

    I downloaded a linux driver for a PCI card peripheral and did an initial 'make' and got errors. The main directory makefile goes through 3 subdirectories to make each of those, and firstly these lines in one of the subdir makefiles seem to cause grief:
    Code:
    ifeq ($(LINUX_VERSION),2.6)
    all: 
    	$(MAKE) -C $(LINUX_SRC) SUBDIRS=$(PWD) modules
    
    rocket.o: $(OBJ).o $(OBJ).c $(OBJ)_int.h $(OBJ).h
    endif
    It echoes that line "make -C SUBDIRS=[working dir] modules" then says "Entering an unknown directory", followed by an no such directory Error 2.

    Continuing to the other subdirs, it returns this Error 1 for the both of them:
    Code:
    /usr/bin/ld: unrecognized option '--build-id'
    /usr/bin/ld: use the --help option for usage information
    collect2: ld returned 1 exit status
    And then fails all with Error 2.
    Anyone know what's up?

  2. #2
    Just Joined!
    Join Date
    Nov 2007
    Posts
    8
    Well the second two errors were fixed with an updated version of binutils. But the first error is still there.

    *Edit: Clarification from the makefile comments:

    Code:
    # To compile just this directory run
    #   make -C <kernel soure directory> SUBDIRS=. modules
    I replaced $(PWD) with a perdiod as the comments said, but still the unknown directory errors...

  3. #3
    Linux Enthusiast
    Join Date
    Aug 2006
    Posts
    631
    It seems that you need to install the kernel source.
    Google for how to install the kernel source for your distro and install the right version that match your kernel.
    Check your release with:

    Code:
    uname -r
    Regards

  4. #4
    Just Joined!
    Join Date
    Nov 2007
    Posts
    8
    Yep, I needed the kernel source - except that actually changed the error to something totally new. I had a feeling this new error is related to the kernel, so I posted in the kernel subforum:
    No modpost directory error

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
...