systemtap compile fail on F18(i686) and F19(i686)

systemtap compile fail on F18(i686) and F19(i686)

[Masanari Iida]

Hello.
After commit id 3d0a328dd, compile systemtap on F18(i686)
and F19(i686) failed.  This symptom can be reproduced only on i686.
Before 3d0a328dd, it can be compiled without error even on i686.

Error messages
  CXXLD    stap
/bin/ld: stap-main.o: undefined reference to symbol
'pthread_create@@GLIBC_2.1' /bin/ld: note: 'pthread_create@@GLIBC_2.1'
is defined in DSO /lib/libpthread.so.0 so try adding it to the linker command
line /lib/libpthread.so.0: could not read symbols: Invalid operation
collect2: error: ld returned 1 exit status
make[2]: *** [stap] Error 1

Workaround.
Add  LDFLAGS = -pthread  in Makefile.

If I compile the snapshot-20130504 on RHEL6, it can be compiled
successfully on both i686 and x86_64 case without error.
So I guess the problem exist on F18(i686) and F19 (i686).

I would like to report this error to Red Hat Bugzilla.
In that case which component do I want to select?

TIA

Masanari Iida

Re: systemtap compile fail on F18(i686) and F19(i686)

[David Smith]

On 05/09/2013 10:44 AM, Masanari Iida wrote:
> Hello.
> After commit id 3d0a328dd, compile systemtap on F18(i686)
> and F19(i686) failed.  This symptom can be reproduced only on i686.
> Before 3d0a328dd, it can be compiled without error even on i686.
> 
> Error messages
>   CXXLD    stap
> /bin/ld: stap-main.o: undefined reference to symbol
> 'pthread_create@@GLIBC_2.1' /bin/ld: note: 'pthread_create@@GLIBC_2.1'
> is defined in DSO /lib/libpthread.so.0 so try adding it to the linker command
> line /lib/libpthread.so.0: could not read symbols: Invalid operation
> collect2: error: ld returned 1 exit status
> make[2]: *** [stap] Error 1
> 
> Workaround.
> Add  LDFLAGS = -pthread  in Makefile.
> 
> If I compile the snapshot-20130504 on RHEL6, it can be compiled
> successfully on both i686 and x86_64 case without error.
> So I guess the problem exist on F18(i686) and F19 (i686).
> 
> I would like to report this error to Red Hat Bugzilla.
> In that case which component do I want to select?

We'd probably prefer you filing the bug at sourceware.org/bugzilla, our
real upstream. In that bugzilla, you'd file it on the "systemtap"
product, then the "translator" component.

In general though, don't worry about the right component, we can always
adjust that later. Go ahead and file the bug.

-- 
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)

Re: systemtap compile fail on F18(i686) and F19(i686)

[Frank Ch. Eigler]

Masanari Iida <standby24x7@gmail.com> writes:

> [...]
> Workaround.
> Add  LDFLAGS = -pthread  in Makefile.
> [...]

That's more than a workaround, that's a fix.  We can simply commit it.

> I would like to report this error to Red Hat Bugzilla.
> In that case which component do I want to select?

If using sourceware.org/bugzilla, it doesn't much matter which
subcomponent of systemtap you select; "releng" is perhaps the most
appropriate one.  If you mean redhat.com/bugzilla, then systemtap is
not subdivided into subcomponents there.

But for this case, where it's minor and the fix is already available,
you don't really have to file a bug at all.

- FChE