There is some ROOTSYS badness in TGQt which has to be fixed. I'll also take
care of the test program problems using the attached patches.
Cheers, Fons.
Roland Kuhn wrote:
> Hi Christian!
>
> On 30 Oct 2006, at 12:20, Christian Holm Christensen wrote:
>
>>>> Try unsetting the ROOTSYS environment variable (and LD_LIBRARY_PATH >>>> for >>>> that matter). These variables are _not_ needed. >>>> >>> Without the Qt plugin it gave no errors, but with it I got >> >> So, if you unset ROOTSYS, it works? Is that correctly understood? >>
>>> rkuhn_at_rk:~$ root >>> Error in <TUnixSystem::ExpandFileName>: input: $ROOTSYS/bin/root.exe, >>> output: $ROOTSYS/bin/root.exe >>> Xlib: extension "XInputExtension" missing on display "localhost:10.0". >> >> I guess this has to do with the remote X server set-up. It's probably >> harmless. >>
>>> Failed to get list of devices\ >> >> Does the pointer and keyboard work? >>
>>> ** $Id: TGQt.cxx,v 1.33 2006/10/04 16:08:48 antcheva Exp $ this=0xb12a70 >>> The font "symbol.ttf" was not installed yet >>> Substitute it with "Arial" >>> Make sure your local "~/.fonts.conf" or "/etc/fonts/fonts.conf" file >>> points to "$ROOOTSYS/fonts" directory to get the proper support for >>> ROOT TLatex class >>> Error in <TUnixSystem::ExpandFileName>: input: $ROOTSYS/cint/include/ >> ... <bla bla bla> >> >> All these warnings has to do with some bugs in the Qt code. The problem >> is, that the Qt code does not take into account that one might install >> ROOT without the use of the ROOTSYS environment variable (sigh!). I'll >> open a bug report on savannah.cern.ch and add a fix. >>
>>> To check e.g. library loading I tried 'gSystem.Load("libPhysics.so")' >>> and got again two Errors with qt and none without. The library seems >>> to work, though. >> >> That's because the Qt backend adds wrong stuff to the library path. >>
>>> I'm doing some stress tests now. >> >> Great. As far as I can tell, they all work, right? >>
>>> I've not noticed any failures (stressGraphics seems to require the >>> creation of a file which I cannot write as non-root, >> >> Probably since you're executing in a directory where you have no write >> access. I'd suggest copying the `test' directory somewhere else (as a >> normal user) and compile and run it there. >>
>>> stressHepix >>> seems to want to call only the other stress tests, which fails >>> because I don't have '.' in my PATH, and I shouldn't be forced to). >> >> No you shouldn't. This is a mistake in the stressHepix program to >> assume that. >> >> Having `.' in ones path is very _very_ bad and is frowned upon by any >> serious administrator. Suppose you have `.' in your PATH, and you cd >> to some other users directory. There you execute `ls'. Now, what you >> don't know, is that the other user has put a malicious version of `ls' >> in her directory, say something that forks and runs some bad stuff in >> the background, while executing `/bin/ls' in the foreground. >>
>> Someone please correct the function `runTest' in `stressHepix.cxx' to >> read >> >> void runTest(const char *atest, int estimate) { >> printf("Running : %s, (takes %d RT seconds on the ref >> machine)\n",atest,estimate); >> gSystem->Exec(Form("./%s >>stressHepix.log",atest)); >> } >>
-- Org: CERN, European Laboratory for Particle Physics. Mail: 1211 Geneve 23, Switzerland E-Mail: Fons.Rademakers_at_cern.ch Phone: +41 22 7679248 WWW: http://fons.rademakers.org Fax: +41 22 7669640Received on Mon Oct 30 2006 - 15:28:19 MET
This archive was generated by hypermail 2.2.0 : Mon Jan 01 2007 - 16:32:01 MET