Rene - I tried your suggestion of adding 'Unix.*.' in front of the macro path specification, but it doesn't seem to fix the problem, which I have now reproduced in several 2.23 releases (most recently, 2.23/09) and on both SunOS5 and Linux architectures. I have included my original post below. Note that omitting 'Unix.*.' seems to work fine for the dynamic library path and for RInt command completion. Another problem I noticed while investigating this, which may be related, is that gEnv->Print() fails on SunOS5 in 2.23/09 (but works on Linux): root [0] gEnv->Print(); Unix.*.Root.DynamicPath: .:/afs/slac.stanford.edu/g/babar/package/root/2.23-09/SunOS5/lib:RELEASE/shlib/SunOS5:PARENT/shlib/SunOS5 [Local] Unix.*.Root.MacroPath: .:/afs/slac.stanford.edu/g/babar/package/root/2.23-09/SunOS5/macros:RELEASE:PARENT [Local] *** Break *** segmentation violation Root > Any more suggestions? cheers, David On Thu, 2 Dec 1999, Rene Brun wrote: > The following should work > Unix.*.Root.MacroPath: .:..:$(ROOTSYS)/macros > On Tue, 30 Nov 1999, David Kirkby wrote: > > > Hello - I am having trouble loading a macro in my search path. I have > > tested the following with 2.23/09: > > > > root [0] .L RooFitTools/RooFitTest.cc > > Error in <TRint::ProcessLine>: macro RooFitTools/RooFitTest.cc not found in path .. > > root [1] .L ../RooFitTools/RooFitTest.cc > > > > > > My .rootrc contains the single line: > > > > Root.MacroPath: .. > > > > Any ideas? It looks like RInt knows about my path since it correctly > > prints it in the error message. Command completion does list this file > > via the search path, and adding the '..' by hand also works. > > > > David
This archive was generated by hypermail 2b29 : Tue Jan 04 2000 - 00:43:44 MET