No rule to make target ...driver/ctf_hash.o

[msabramo]

make -C /lib/modules/2.6.32-38-generic/build M=/home/marca/src/dtrace4linux/linux/build-2.6.32-38-generic/driver
  LD      /home/marca/src/dtrace4linux/linux/build-2.6.32-38-generic/driver/built-in.o
make[3]: *** No rule to make target `/home/marca/src/dtrace4linux/linux/build-2.6.32-38-generic/driver/ctf_hash.o', needed by `/home/marca/src/dtrace4linux/linux/build-2.6.32-38-generic/driver/dtracedrv.o'.  Stop.
make[2]: *** [_module_/home/marca/src/dtrace4linux/linux/build-2.6.32-38-generic/driver] Error 2
make[1]: *** [kernel] Error 2
tools/bug.sh
======================
== Sorry - but dtrace failed to compile on your system.
== Please forward the following file to:
==
== file: /tmp/dtrace-bug.25778
== mail: dtrace@crisp.demon.co.uk
==
== and the information provided will be used to help
== enhance the tool and fix the underlying issue.
==
== Latest news and blog updates on dtrace available here. Please
== check for latest problem reports.
==
== http://crtags.blogspot.com
== http://www.crisp.demon.co.uk/blog/
==
== Latest downloads available from here:
==
== ftp://crisp.dyndns-server.com/pub/release/website/dtrace
== ======================
(generating a make run - this may take a few moments...)

[dtrace4linux]

this shouldnt be necessary. first thing we do is symlink the sources so we can build in the build/driver directory. (I did this because there was an issue I couldnt easily resolve in the Linux Makefile structure).

[msabramo]

Hmm, something must not be working as expected then.

marca@ubuntu:~/src/dtrace4linux$ git clone https://github.com/dtrace4linux/linux.git dtrace4linux-test && cd dtrace4linux-test && make all
...

symlink ../../driver/dis_tables.h build-2.6.32-38-generic/driver/dis_tables.h
symlink ../../driver/dtrace_linux.h build-2.6.32-38-generic/driver/dtrace_linux.h
symlink ../../driver/dtrace_proto.h build-2.6.32-38-generic/driver/dtrace_proto.h
symlink ../../driver/intr_x86-32.S build-2.6.32-38-generic/driver/intr_x86-32.S
symlink ../../driver/intr_x86-64.S build-2.6.32-38-generic/driver/intr_x86-64.S
Executing: /home/marca/src/dtrace4linux/dtrace4linux-test/tools/make-me
make -C /lib/modules/2.6.32-38-generic/build M=/home/marca/src/dtrace4linux/dtrace4linux-test/build-2.6.32-38-generic/driver
  LD      /home/marca/src/dtrace4linux/dtrace4linux-test/build-2.6.32-38-generic/driver/built-in.o
make[3]: *** No rule to make target `/home/marca/src/dtrace4linux/dtrace4linux-test/build-2.6.32-38-generic/driver/ctf_hash.o', needed by `/home/marca/src/dtrace4linux/dtrace4linux-test/build-2.6.32-38-generic/driver/dtracedrv.o'.  Stop.
make[2]: *** [_module_/home/marca/src/dtrace4linux/dtrace4linux-test/build-2.6.32-38-generic/driver] Error 2
make[1]: *** [kernel] Error 2
...

[msabramo]

So I see that tools/mkdriver.pl symlinks a bunch of files in driver to $ENV{BUILD_DIR}/driver, but ctf_hash.c is in common/ctf/ctf_hash.c. libctf/makefile does this with it:

$(BINDIR)/libctf.a(ctf_hash.o): $(COMMON)/ctf_hash.c
        $(CC) $(CPPFLAGS) -c $<
        $(AR) rv $(BINDIR)/libctf.a ctf_hash.o
        rm -f ctf_hash.o

so there is no ctf_hash.o; only libctf.a and common/ctf/ctf_hash.c.

[dtrace4linux]

resolved by adding missing file to github

[mintberry]

issue open again, when make all

make[3]: *** No rule to make target /home/neon/Downloads/linux-master/build-3.2.0-37-generic-pae/driver/ctf_hash.o', needed by /home/neon/Downloads/linux-master/build-3.2.0-37-generic-pae/driver/dtracedrv.o'. Stop.'

maybe it's because the latest kernel?

[dtrace4linux]

Pae mode kernels likely wont compile...but the issue here is likely a
poluted compilation environment or env vars conglicting with the linux build
On Feb 1, 2013 4:34 AM, "Neo Qi" notifications@github.com wrote:

issue open again, when make all

make[3]: *** No rule to make target /home/neon/Downloads/linux-master/build-3.2.0-37-generic-pae/driver/ctf_hash.o',
needed by/home/neon/Downloads/linux-master/build-3.2.0-37-generic-pae/driver/dtracedrv.o'.
Stop.

maybe it's because the latest kernel?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-12980413.