[MacPorts] #26669: mesa @7.8.2_2 installation => conflict with /System libGL.dylib

[MacPorts]

#26669: mesa @7.8.2_2 installation => conflict with /System libGL.dylib
-------------------------------------------+--------------------------------
 Reporter:  karl.hauschild@…               |       Owner:  jeremyhu@…           
     Type:  defect                         |      Status:  new                  
 Priority:  Normal                         |   Milestone:                       
Component:  ports                          |     Version:  1.9.1                
 Keywords:                                 |        Port:  mesa                 
-------------------------------------------+--------------------------------

Comment(by karl.hauschild@…):

 To be honest I can not remember why I put


 {{{
 DYLD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/local/lib
 }}}


 It might have been that some old instructions for macports installation
 stated that one should do this. Google pops up a few blogs that
 corroborate this. It[[BR]]
 might just be that I did this from prior experience with other software
 installations.

 However, if a DYLD_* is not set then this is what one gets when trying to
 run an example compiled using the geant4 package.


 {{{
  [hauschild] : TestEm5
 dyld: Library not loaded: libiAIDA.dylib
   Referenced from: /Users/hauschild/geant4/bin/TestEm5
   Reason: image not found
 Trace/BPT trap
 }}}


 This very same example worked with the previous version of geant4 that I
 had compiled myself from source and for which I had defined


 {{{
 #GEANT4.9.2
 . /Users/hauschild/applications/geant4.9.2/src/geant4/env.sh
 export DYLD_LIBRARY_PATH=$DYLD_LIBRARY_PATH:$APPS/CLHEP/lib
 }}}


 so this might be the source of my DYLD'ing......[[BR]]
 [http://geant4.slac.stanford.edu/tutorial/installation/Geant4.9.3.p01/Mac/Geant4_9_3_p01_Mac_Installation.htm#_The_Geant4_Work]
 [[BR]]
 [[BR]]
 The upshot is : IF I want software compiled using the geant4 framework
 which has been[[BR]]
 installed using macports to work along side system commands like "open" I
 must set


 {{{
 DYLD_FALLBACK_LIBRARY_PATH=$DYLD_FALLBACK_LIBRARY_PATH:/opt/local/lib
 }}}


 From a quick test with ROOT5.26 installed using macports it appears that I
 do not have to set any *LD*_LIBRARY_PATH[[BR]]
 to compile and run my own codes.

 So - is it really a problem with my configuration (as stated in an earlier
 ticket without helpful explanation) or is it a problem that[[BR]]
 some packages do not have the library paths hard-coded.

 Cheers,
 Karl

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