[Xen-bugs] [Bug 628] New: Tools contain hardcoded paths, and hence don't work with DESTDIR

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=628

           Summary: Tools contain hardcoded paths, and hence don't work with
                    DESTDIR
           Product: Xen
           Version: 3.0 (general)
          Platform: x86-64
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P2
         Component: Tools
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: tethys@xxxxxxxxx


As a general priciple, it's a bad idea to mix system managed binaries with
self compiled ones. Thus I wanted to install the Xen tools under /opt/xen.

The README claims "You can override the destination for make install by
setting DESTDIR to some value.". Sounds ideal. However, while:

DESTDIR=/opt/xen make install

does indeed put the appropriate files under /opt/xen, they don't work.
Firstly, I had to set LD_LIBRARY_PATH and PYTHONPATH to point to the
right place, just to get xend to run at all. But then it just fails
because it can't find the config file. I had to do a recursive grep
just to find out where it was looking for this file (XendRoot.py, as
it turns out), and then read the source to spot that I can override
the default by using the XEND_CONFIG environment variable.

Really, "make install" should notice that and alternative DESTDIR is
being supplied, and make appropriate changes to provide some sensible
defaults. But at the very least, the necessary changes should be
documented somewhere obvious.

Currently, I still don't have a running xend.


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs