[Bug 208034] Review Request: HippoDraw - Interactive and Python scriptable data analysis application

bugzilla at redhat.com bugzilla at redhat.com
Sat Oct 7 00:45:00 UTC 2006


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: HippoDraw - Interactive and Python scriptable data analysis application


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





------- Additional Comments From tibbs at math.uh.edu  2006-10-06 20:44 EST -------
This failed to build for me in mock on x86_64 rawhide and fc5 i386.  Configure
dies when doing the Qt checks:

checking for Qt... ./configure: line 22007: test: xno: unary operator expected
yes:
    QT_CXXFLAGS=-I/usr/lib64/qt-3.3/include -DQT_THREAD_SUPPORT
    QT_DIR=/usr/lib64/qt-3.3
    QT_LIBS=-L/usr/lib64/qt-3.3/lib -lqt-mt  -lSM -lICE  -lX11 -lXext -lXmu -lXt
-lXi  -R/usr/lib64/qt-3.3/lib
    QT_UIC=/usr/lib64/qt-3.3/bin/uic
    QT_MOC=/usr/lib64/qt-3.3/bin/moc
checking correct functioning of Qt installation... failure
configure: error: Failed to find matching components of a complete
                  Qt installation. Try using more options,
                  see ./configure --help.
error: Bad exit status from /var/tmp/rpm-tmp.57891 (%build)

The "xno" error comes from this line:
    if test x$enable_rpath =xno; then
which is missing a space before "xno".  I don't know if this results in the
failure to find Qt or not.

Also in the configure output:
configure: checking boost installation with
    BOOST_LDFLAGS=-lboost_python
checking for /usr/lib/libboost_python.so... no
configure: WARNING:
        Build will fail to build Python module, the last step

Looks like it's looking in /usr/lib on an x86_64 system.

Is Fortran required anywhere?  The configure script checks for it (and doesn't
find it) but I don't think it's used.

Are Minuit2, ROOT or WCSLIB expected to be found?  They're not on my system.

How do you run the included test suite?

You know you don't have to separately list out your BuildRequires:, right?  You
can if you like, but in the end it just takes the union of all of them.

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.




More information about the package-review mailing list