From: Brian P. <bri...@tu...> - 2005-03-31 15:02:12
|
I had fixed a similar problem in the glloader.c file, but missed this. This is actually an interesting issue. The SYSTEM_LIB_DIR value should either be /usr/lib/ or /usr/lib64/ depending on whether the application is 32 or 64-bit. But I'm not sure how to determine that from within the crappfaker. The crappfaker uses fork() to spawn the application. So crappfaker could be 32-bit while the application is 64-bit, or vice versa. If we were to assume that the crappfaker and application were both 32 or 64-bit that would simplify things. I'd have to study the appfaker.c code for a while. I've never touched it before. Ideas are welcome. -Brian Abhijit Gadgil wrote: > Actually the problem is - > > In the app_faker/app_faker.c the SYSTEM_LIB_PATH is set to "/usr/lib" even for > x86_64, which should be /usr/lib64. > > Changing that, things work without a symlink. (I was using Mesa OpenGL) > > Thanks > > -abhijit > > > > --- Brian Paul <bri...@tu...> wrote: > >>Abhijit Gadgil wrote: >> >>>Hi all, >>> >>>I am using the latest chromium (1.8) on AMD Opteron motherboard. The >> >>problem I >> >>>am facing is as follows - >>>When any application is started using crdemo.conf file, the mothership runs >>>properly and the crserver runs properly. However, when crappfaker is >> >>invoked >> >>>following different behavior is observed in two different scenarios >>> - When /usr/lib64/libGL.so is symlinked to /usr/lib/ the crappfaker runs >>>properly. >>> - When /usr/lib64 is not symlinked to /usr/lib/libGL.so the crappfaker is >>>running as the application would run when fired from a command line. >>> >>>Strangely enough in the glloader.c systemPath is shown as /usr/lib64, which >>>means that there is no dependency on /usr/lib/libGL.so >>> >>>Can anyone throw some light on this? >> >>I assume you compiled Chromium in 64-bit mode. >> >>Is /usr/lib/libGL.so a 64-bit library? >> >>Whose OpenGL are you using? >> >>With the NVIDIA drivers, you should have both 32 and 64-bit libraries >>in the /usr/lib/ and /usr/lib64/ directories, respectively. There >>should be no reason to make symlinks. >> >>-Brian >> > > > > > __________________________________ > Do you Yahoo!? > Yahoo! Small Business - Try our new resources site! > http://smallbusiness.yahoo.com/resources/ > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Chromium-users mailing list > Chr...@li... > https://lists.sourceforge.net/lists/listinfo/chromium-users > |