mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Aubrey <aubreylee@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: The assemble file under the driver folder can not be recognized when the driver is built as module
Date: Mon, 10 Apr 2006 18:16:56 +0800	[thread overview]
Message-ID: <6d6a94c50604100316j43bcc32p6fa781c0ce47182d@mail.gmail.com> (raw)

Hi all,

I've written a framebuffer driver and put it under the folder
"./drivers/video", it consists of two files" mydriver.c and myfun.S".
When I build it into the kernel image, everything is ok.
But when I build it as module, I got the following error message:
===========================================
aubrey@linux:~/cvs/kernel/uClinux-dist> make V=1
--------snip---------
make -f scripts/Makefile.build obj=drivers/video
make -f scripts/Makefile.build obj=drivers/video/backlight
make[3]: *** No rule to make target `drivers/video/rgb2ycbcr.c',
needed by `drivers/video/rgb2ycbcr.o'.  Stop.
make[2]: *** [drivers/video] Error 2
make[1]: *** [drivers] Error 2
make[1]: Leaving directory `/home/aubrey/cvs/kernel/uClinux-dist/linux-2.6.x'
make: *** [linux] Error 1
===========================================

Make ask me for ".c" file. But it's an assemble file indeed.
Is it a bug of kernel script? (I'm using 2.6.16)

Regards,
-Aubrey

             reply	other threads:[~2006-04-10 10:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-10 10:16 Aubrey [this message]
2006-04-10 11:28 ` Erik Mouw
2006-04-10 13:27   ` Aubrey
2006-04-10 17:33     ` Sam Ravnborg
2006-04-10 17:42     ` Adrian Bunk
2006-04-10 18:04       ` linux-os (Dick Johnson)
2006-04-10 18:24         ` Sam Ravnborg
2006-04-10 19:12           ` linux-os (Dick Johnson)
2006-04-10 19:30             ` Sam Ravnborg
2006-04-11  2:58         ` Aubrey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6d6a94c50604100316j43bcc32p6fa781c0ce47182d@mail.gmail.com \
    --to=aubreylee@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®