[MacPorts] #38236: root 5.34.05_0 still broken after rebuilding 3 times

MacPorts noreply at macports.org
Thu Feb 28 14:57:49 PST 2013


#38236: root 5.34.05_0 still broken after rebuilding 3 times
----------------------------+-----------------------------------
  Reporter:  andre.david@…  |      Owner:  mattiafrancescomoro@…
      Type:  defect         |     Status:  new
  Priority:  Normal         |  Milestone:
 Component:  ports          |    Version:  2.1.3
Resolution:                 |   Keywords:
      Port:  root           |
----------------------------+-----------------------------------

Comment (by andre.david@…):

 Replying to [comment:11 jonesc@…]:
 > It looks like you have an another installation of ROOT/xrootd under
 /opt/xrootd. MacPorts would not have put that there, so you must have
 installed it some other way as MacPorts *only* puts things in /opt/local
 (at least by default, you could have changed something in the
 configuration).

 So, consulting my logs, I did install `xrootd` in `/opt/xrootd`.
 And `sudo port install --no-rev-upgrade root
 +fftw3+graphviz+gsl+minuit2+opengl+pythia+python27+roofit+soversion+ssl+tmva+xml`
 works as a temporary patch.

 But this is overall nasty. From what I understand, `rev-upgrade` does not
 know about `/opt/xrootd/lib` presumably because it is not run as myself
 (`sudo` dixit). As myself, I have
 {{{
 export ROOTSYS=/opt/local
 if [ -f ${ROOTSYS}/bin/thisroot.sh ]; then
   . ${ROOTSYS}/bin/thisroot.sh
   source ${ROOTSYS}/bin/setxrd.sh /opt/xrootd
 }}}

 which leads to
 {{{
 $ echo $LD_LIBRARY_PATH
 /opt/xrootd/lib
 }}}

 So, this is still an issue that may be solved with some help from the
 Macports gurus:

 ''Is there a generic way to pass an extra path that `rev-upgrade`
 checks?''

-- 
Ticket URL: <https://trac.macports.org/ticket/38236#comment:12>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list