[Bug 445224] Review Request: stapitrace - user space instruction trace

bugzilla at redhat.com bugzilla at redhat.com
Mon Jun 23 23:48:34 UTC 2008


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: stapitrace - user space instruction trace


https://bugzilla.redhat.com/show_bug.cgi?id=445224





------- Additional Comments From dcnltc at us.ibm.com  2008-06-23 19:48 EST -------
> > > package meets naming and versioning guidelines.
> > > package builds in mock:
> > > http://koji.fedoraproject.org/koji/getfile?taskID=664952&name=build.log
I think the problem in the build was because configure didn't really work.
What kind OS was on your test machine?  I think the crux of the problem is in
the output from configure:
--------------------------------------------------------------------------
CPU = powerpc64, OS = linux-gnu, Vendor = redhat, HostType = powerpc64
--------------------------------------------------------------------------
ERROR: Platform powerpc64 not yet supported

On the fedora9 ppc machine I tried I got:
--------------------------------------------------------------------------
CPU = powerpc64, OS = linux-gnu, Vendor = redhat, HostType = powerpc
--------------------------------------------------------------------------

So, it is HostType=powerpc vs HostType=powerpc64.  On my machine I don't get
this configuration error.  

What does config.guess return on your machine?

On my Fedora9 ppc machine I get:
powerpc64-redhat-linux-gnu

which is the same thing I see in a RHEL5.2 ppc machine.

If you think that the configure script should be able to handle the
HostType=powerpc64, I can go ahead and patch the configure.in.

> > > package installs properly. (couldn't check)
> > > debuginfo package looks complete. (couldn't check)
> > > final provides and requires are sane (couldn't check)
> > > if shared libraries are present, make sure ldconfig is run
What does this mean by "couldn't check"? I was unable to do hardly any testing
on the fedora9 machine because I couldn't find compatible pieces like
binutils-devel since my machine is in ABAT.  I spent about a week some time ago
trying to get Fedora9-alpha installed from CDs on a ppc machine but never could
get it to work.

> 
> That, and the naming.  See below.
> 
What is the naming issue?

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




More information about the Fedora-package-review mailing list