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
... cut ...
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),
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
I might take a look at this, this weekend, if I have time.
Unfortunately, the set up required is a deterrring factor.
This would seem to be an excellent example of the use of a virtual machine
... with a standard virtual machine with Ubuntu on it, Rony could do the
minimum setup (added
On 8/11/2010 at 04:12 PM, in message
4c62a1a6022400055...@novprvlin0050.provo.novell.com, Erico Mendonca
emendo...@novell.com wrote:
BUT, I'm getting error on TEST_006 on SLES 11SP1 if I try to use the same build
as SLES 11:
Okay, apparently the test was failing because the
Hi Mark,
On 16.08.2010 19:02, Mark Miesfeld wrote:
I know how frustrating these types of things can be. (But, it is very
satisfying if you solve them.)
Indeed, at the moment it is superfrustrating, probably because I am a
little bit outworn working for weeks now on overhauling the
On 16.08.2010 19:27, Mike Cowlishaw wrote:
I might take a look at this, this weekend, if I have time.
Unfortunately, the set up required is a deterrring factor.
This would seem to be an excellent example of the use of a virtual machine
... with a standard virtual machine with Ubuntu on
Hmmm, taking a quick look at the code and the places where the file
unreadable error can be triggered, I found the following lines in
FileSystem.cpp:
RexxBuffer *SystemInterpreter::readProgram(const char *file_name)
/***/
/*
Right now the build machine is in a sort of transition state. All the nightly
builds are running (with the exception of Win XP) but I need to install a new
network card in the new machine before I can start giving access to VMs. I
should have the card this week sometime.
What version of
O.K., here is one more piece of information which may be helpful.
Running one of those Rexx programs that cause that error this way from
rexxtry.rex fails:
call testOOo.rxo
whereas the following works:
cmd=rexx testOOo.rxo
say cmd
cmd
Here are additional variations of
On 16.08.2010 20:38, David Ashley wrote:
Right now the build machine is in a sort of transition state. All the
nightly
builds are running (with the exception of Win XP) but I need to install a new
network card in the new machine before I can start giving access to VMs. I
should have
11 matches
Mail list logo
