Re: systemtap multiple objs linking question

[Jan W <jcwynholds at gmail dot com>]

Here is the build log:

$ make -j8 | tee -a build.log

The makefiles are nested, so if you want to check those out, clone my
branch and run configure

src/node_systemtap.d
generates
node_systemtap.h
node_sytemtap_sema.o

src/node_systemtap.cc
generates an .o

looked to me like linker was trying to get all objects on the final
link of src/out/node.

Thanks again!


Attached is the build.log.  Thanks!

On Mon, Oct 15, 2012 at 7:07 AM, Frank Ch. Eigler <fche@redhat.com> wrote:
>
> Hi -
>
>> [...]
>> got all the definitions for the probes (a .d make dtrace -> .h and .o), but
>> it's failing on final link of node due to undefined references.
>> node/out/Release/obj.target/node/src/node_systemtap.o:(.note.stapsdt+0x378):
>> undefined reference to `net__socket__write_semaphore'
>> [...]
>
>> The provider names are in the generated obj, but the linker is failing to
>> find the symbols that should be pointing to notes sections (right??)
>
> Could you paste complete command lines and the tail end of the make
> transcript?  It's as though that generated .o file is not being handed
> to the linker.
>
>> =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
>> Sent from my brain.
>> =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
>
> Nice squishyware advertisement!
>
> - FChE



-- 
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
Sent from my brain.
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=

Attachment: build.log
Description: Binary data