On 6/26/05, Daniel Jarboe <daniel.jarboe@gmail.com> wrote:
> If it has its own Makefile (check its directory), just do a make in that
> directory. If not you could try to create a target in the Makefile you are
> using, or make a makefile just for it in the same directory (look for
> Makefiles for other modules to guide you).
>
Here is the directory contents as you can see there is a Makefile in
there.
root@fpac-dev:/usr/src/kernel-source-2.4.22-xfs/net/rose# ls
Makefile rose_dev.c rose_loopback.c rose_subr.c
af_rose.c rose_in.c rose_out.c rose_timer.c
af_rose.c.old rose_link.c rose_route.c sysctl_net_rose.c
root@fpac-dev:/usr/src/kernel-source-2.4.22-xfs/net/rose#
If I do a make on it here is what I get
root@fpac-dev:/usr/src/kernel-source-2.4.22-xfs/net/rose# make
Makefile:18: /Rules.make: No such file or directory
make: *** No rule to make target `/Rules.make'. Stop.
root@fpac-dev:/usr/src/kernel-source-2.4.22-xfs/net/rose#
I see a Rules.make in the main directory /usr/src/kernel-2.4.22.xfs
But that I assume is rules for the whole source. I even tried it in
the rose directory but no joy...
-- Chuck Hast To paraphrase my flight instructor; "the only dumb question is the one you DID NOT ask resulting in my going out and having to identify your bits and pieces in the midst of torn and twisted metal."----------------------------------------------------------------------- This list is provided as an unmoderated internet service by Networked Knowledge Systems (NKS). Views and opinions expressed in messages posted are those of the author and do not necessarily reflect the official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:34:16 EDT