Handle semaphore compilation / dtrace on linux

[viraptor]

I'm not sure exactly what the differences are between the system where this was tested and mine, I ran into the problem described in issue #1 .
The build failed first because of an -arch dtrace argument not available on my system (comes from systemtap 4.5). This was made an optional argument (default off).
Then it failed because of the semaphore file not being linked in. This was solved by adding an option to either compile without the semaphore object file (original behaviour, default), or to explicitly generate it (option).

If this doesn't play well with other systems this library was tested on, I'm happy to put some cfg guards around the functionality.

Fixes #1

[viraptor]

Not sure if this is monitored, so pinging @Hywan

[viniciusd]

Does this fix look acceptable @Hywan?

I am having the same issue described at #1

[Hywan]

I'm no longer working for Wasmer. You should ping @syrusakbary for that.

[viniciusd]

I'm no longer working for Wasmer. You should ping @syrusakbary for that.

Thanks for sharing! Wish you all the best in your new path

[No9]

@viniciusd Thanks for putting together this patch.

@syrusakbary This patch works as expected and I would like to add to the docs to illustrate the linux eBPF scenario wtih tplist and bpftrace syntax.

Would it be possible to land this?

[viniciusd]

@viniciusd Thanks for putting together this patch.

@syrusakbary This patch works as expected and I would like to add to the docs to illustrate the linux eBPF scenario wtih tplist and bpftrace syntax.

Would it be possible to land this?

I wish I were responsible for the changes, but I cannot take @viraptor's credits. Either way, looking forward to having it merged (and thanks @viraptor)

[No9]

Sincere Apologies @viraptor
I was fooled by the autocomplete.
Thanks @viniciusd for the correction