Menu
▾
▴
Re: [Oorexx-devel] Request for help on (Ubuntu) Linux (32- and 64-bit)
|
From: Mark M. <mie...@gm...> - 2010-08-16 17:02:38
|
Hi Rony, I know how frustrating these types of things can be. (But, it is very satisfying if you solve them.) I might take a look at this, this weekend, if I have time. Unfortunately, the set up required is a deterrring factor. Until then: I would try with a build from trunk. David has the build machine working well and you could easily pick up a pre-built deb package with all the latest fixes. I would try putting all the required files in the same diretory you are executing your script from, just to see what happens. Of course, you may have already tried these things. -- Mark Miesfeld On Mon, Aug 16, 2010 at 9:31 AM, Rony G. Flatscher <Ron...@wu...> wrote: > Hi there, > > after experimenting the whole day, I have not yet come to a conclusion about > the cause of a runtime problem I have been experiencing with ooRexx 4.0.1 on > 32- and 64-bit Ubuntu: > > when requiring "UNO.CLS" which requires other Rexx packages itself, an error > along the following lines occurs: > > rony@ronylinux:/opt/BSF4ooRexx/install$ rexx /usr/bin/UNO.CLS > 318 *-* ::requires UNO_XINTERFACES.RXO -- get the list of all of UNO > XInterface classes > EX0003E: Error 3 running /usr/bin/UNO.CLS line 318: Failure during > initialization > EX0200E: Error 3.1: Failure during initialization: File > "/usr/bin/UNO_XINTERFACES.RXO" is unreadable > rony@ronylinux:/opt/BSF4ooRexx/install$ > > > it seems to be positional, i.e. if changing the requires statement to > "::requires "rgf_utli2.rex" then the same error occurs but now relating to > "rgf_util2.rex" ! > this error occurs whenever Rexx programs requiring UNO.CLS are invoked from > the command line using the "rexx" executable. Running programs requiring > UNO.CLS via the OpenOffice macro menu works! > all rights on the scripts are set to 755 (rwxr-xr-x), they reside in > "/usr/bin" (as a matter of fact, it does not matter where they reside and > whether they are owned by root or by the user who executes the scripts). > > I have not been able to create a standalone test-set which would exhibit > this behaviour on Linux, unfortunately. :( > > Therefore a request for help/ideas to solve this puzzling problem! > > This would be needed to recreate the problem as I have been facing it: > > get Ubuntu, > uninstall the Ubuntu-OOo via synaptic manager (they tamper with the genuine > OpenOffice, unfortunately, harming the Java interface to OOo, which is > exploited by BSF4ooRexx), > get the matching genuine OOo package by pointing your browser (from within > Linux) to: <http://download.openoffice.org/index.html>, this will place the > genuine OOo installation package that matches your installation on top, > download it, unpack and install it (to install change into the DEB directory > and issue: "" > get the installation package of BSF4ooRexx from this particular location: > <http://wi.wu-wien.ac.at/rgf/rexx/bsf4oorexx/archive/2010/2010-08-16/BSF4ooRexx%5finstall%2ezip> > > unzip it, change into "bsf4oorexx/install" and run "install.sh"; this will > copy the entire package to "/opt/BSF4ooRexx" and proceed from > "/opt/BSF4ooRexx/install/" where the installation and uninstall scripts get > created > after the installation BSF4ooRexx got installed, and now you need to install > the OOo support by running "/opt/BSF4ooRexx/install/reinstall.sh" > > currently it is possible that "unopkg" is not successfully carried out, due > to a leftover lock file in "~/.openoffice/3/.lock" > locate and delete that lock-file, then run "sudo > /opt/BSF4ooRexx/install/installOOo.sh" > check by starting the OOo writer, go to "Tools -> Macros -> Run" and pick > the "HelloWorld" example from the "OpenOffice/ooRexxExamples" macro folder. > > best logoff and logon again (this makes sure that from that point on > "/etc/profile" is honored which sets up the environment for BSF4ooRexx; this > allows one to start BSF4ooRexx scripts also by double-clicking via the > desktop interface of Linux). > > Now, if you open a command line window and go into "/opt/BSF4ooRexx/install" > and run "rexx testOOo.rxo" you should get the above mentioned error! > > Hopefully, you can find a workaround or the cause of this error, which is a > showstopper right now for the Linux platform. > > TIA, > > ---rony > > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > |