Failure to link Ruby 2 about linux HOT 16 CLOSED

I've run into the same problem. How well supported are usdt probes?

from linux.

Did any of you able to identify firing ruby dtrace probes?

from linux.

Just a quick summary. Did the "link" problem get resolved? My USDT test
cases arent far reaching - only simple tests. Real code with various
C/assembler constructs will do more things. In the example below, the
suggestion of -fPIC would suggest thats the only way forward - in x86/64,
most things are relative, and assume a distance within 4GB of addressing,
but thenature of code is that something may be causing a different type of
ELF construct (eg later gcc) or maybe just not enough testing. tx

On 15 June 2013 08:12, Chamila Wijayarathna [email protected]:

Did any of you able to identify firing ruby dtrace probes?

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

from linux.

I can confirm the problem. I cant compile ruby 2.0.0-p0 and 2.0.0-p195 with the dtrace.
After remove the dtrace and install new dtrace by sudo apt-get install systemtap-sdt-dev, then both ruby can be compiled and installed.

from linux.

Hello raykin,
Did you able to compile and execute DTrace probes in Linux? What is the OS
you are using?

On Thu, Jun 20, 2013 at 3:53 PM, raykin [email protected] wrote:

I can confirm the problem. I cant compile ruby 2.0.0-p0 and 2.0.0-p195
with the dtrace.
After remove the dtrace and install new dtrace by sudo apt-get install
systemtap-sdt-dev, then both ruby can be compiled and installed.

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

Chamila Dilshan Wijayarathna,
SMIEEE, SMIESL,
Undergraduate,
Department of Computer Science and Engineering,
University of Moratuwa.

from linux.

Can someone quote what I need to do to reproduce this - just grab the ruby
sources? Do I need a specific config for dtrace or is it autoconfigured?

On 20 June 2013 11:50, Chamila Wijayarathna [email protected]:

Hello raykin,
Did you able to compile and execute DTrace probes in Linux? What is the OS
you are using?

On Thu, Jun 20, 2013 at 3:53 PM, raykin [email protected] wrote:

I can confirm the problem. I cant compile ruby 2.0.0-p0 and 2.0.0-p195
with the dtrace.
After remove the dtrace and install new dtrace by sudo apt-get install
systemtap-sdt-dev, then both ruby can be compiled and installed.

—
Reply to this email directly or view it on GitHub<
https://github.com/dtrace4linux/linux/issues/53#issuecomment-19742638>
.

Chamila Dilshan Wijayarathna,
SMIEEE, SMIESL,
Undergraduate,
Department of Computer Science and Engineering,
University of Moratuwa.

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

from linux.

my OS is ubunt13.04, I just download ruby source and configure and make install.

from linux.

Did you install and load dtrace before the build ?
On 21 Jun 2013 02:22, "raykin" [email protected] wrote:

my OS is ubunt13.04, I just download ruby source and configure and make
install.

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

from linux.

yup, I install the latest dtrace-20130530 and make load, then compile ruby source, then error happened. I not sure if make reload must be needed to trigger error cause I'm a beginner on dtrace

from linux.

I was able to compile and run ruby 2.0 on Ubuntu 11.10 without any problem,
But the system does not identify DTrace probes.

On Fri, Jun 21, 2013 at 1:06 PM, raykin [email protected] wrote:

yup, I install the latest dtrace-20130530 and make load, then compile ruby
source, then error happened. I not sure if make reload must be needed to
trigger error cause I'm a beginner on dtrace

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

Chamila Dilshan Wijayarathna,
SMIEEE, SMIESL,
Undergraduate,
Department of Computer Science and Engineering,
University of Moratuwa.

from linux.

Just an update - i grabbed the ruby sources and reproduced the issue...off
to investigate...

On 21 June 2013 14:53, Chamila Wijayarathna [email protected]:

I was able to compile and run ruby 2.0 on Ubuntu 11.10 without any
problem,
But the system does not identify DTrace probes.

On Fri, Jun 21, 2013 at 1:06 PM, raykin [email protected] wrote:

yup, I install the latest dtrace-20130530 and make load, then compile
ruby
source, then error happened. I not sure if make reload must be needed to
trigger error cause I'm a beginner on dtrace

—
Reply to this email directly or view it on GitHub<
https://github.com/dtrace4linux/linux/issues/53#issuecomment-19802201>
.

Chamila Dilshan Wijayarathna,
SMIEEE, SMIESL,
Undergraduate,
Department of Computer Science and Engineering,
University of Moratuwa.

—

Reply to this email directly or view it on GitHubhttps://github.com//issues/53#issuecomment-19817014
.

from linux.

Ive released a new dtrace to fix this. The drti.o file wasnt compiled with
-fPIC and when I change that, the link with ruby sees to work.

On 21 June 2013 22:16, Paul Fox [email protected] wrote:

Just an update - i grabbed the ruby sources and reproduced the issue...off
to investigate...

On 21 June 2013 14:53, Chamila Wijayarathna [email protected]:

I was able to compile and run ruby 2.0 on Ubuntu 11.10 without any
problem,
But the system does not identify DTrace probes.

On Fri, Jun 21, 2013 at 1:06 PM, raykin [email protected]
wrote:

yup, I install the latest dtrace-20130530 and make load, then compile
ruby
source, then error happened. I not sure if make reload must be needed
to
trigger error cause I'm a beginner on dtrace

—
Reply to this email directly or view it on GitHub<
https://github.com/dtrace4linux/linux/issues/53#issuecomment-19802201>
.

Chamila Dilshan Wijayarathna,
SMIEEE, SMIESL,
Undergraduate,
Department of Computer Science and Engineering,
University of Moratuwa.

—

Reply to this email directly or view it on GitHubhttps://github.com//issues/53#issuecomment-19817014
.

from linux.

Great! I'll give it a try tonight!

from linux.

does it support ruby dtrace probes?

On Sun, Jun 23, 2013 at 3:10 AM, Martin Englund [email protected]:

Great! I'll give it a try tonight!

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

Chamila Dilshan Wijayarathna,
SMIEEE, SMIESL,
Undergraduate,
Department of Computer Science and Engineering,
University of Moratuwa.

from linux.

Yes. The requirement is that dtrace is installed on your system so that
"configure" can find it during the build.

(I havent tried to run the ruby with probes, but Martin can feedback if it
works as expected).

On 23 June 2013 05:45, Chamila Wijayarathna [email protected]:

does it support ruby dtrace probes?

On Sun, Jun 23, 2013 at 3:10 AM, Martin Englund [email protected]:

Great! I'll give it a try tonight!

—
Reply to this email directly or view it on GitHub<
https://github.com/dtrace4linux/linux/issues/53#issuecomment-19865189>
.

Chamila Dilshan Wijayarathna,
SMIEEE, SMIESL,
Undergraduate,
Department of Computer Science and Engineering,
University of Moratuwa.

—

Reply to this email directly or view it on GitHubhttps://github.com//issues/53#issuecomment-19869053
.

from linux.

I forgot to get back with an update - I can get past the linking problem, but am now stuck on another piece crashing. However, that should not be related to the missing -fPIC, so I'm closing this issue.

from linux.