[Oorexx-devel] Problems compiling 64-bit ooRexx for 64-bit Linux (Ubuntu) and installing it

[Rony G. Flatscher]

Hi there,

in the need of a 64-bit ooRexx from trunk, I checked out ooRexx from
Sourceforge.

* Changed into "main/trunk", created a subdir "tmp",
* ran from main/trunk/tmp the command "../conifugre
  --disable-static" followed by "make"
* then issuing a "make install" (to have it installed into
  /opt/ooRexx), but receive the following output with errors at the end:

  r...@ronylinux:~/dev/oorexx/main/trunk/tmp$ sudo make install
  cp ../extensions/rxregexp/rxregexp.cls ./
  cp ../extensions/rxftp/rxftp.cls ./
  cp ../extensions/csvStream/csvStream.cls ./
  cp ../extensions/rxsock/socket.cls ./
  cp ../extensions/rxsock/streamsocket.cls ./
  make  install-recursive
  make[1]: Entering directory `/home/rony/dev/oorexx/main/trunk/tmp'
  make[2]: Entering directory `/home/rony/dev/oorexx/main/trunk/tmp'
  make[3]: Entering directory `/home/rony/dev/oorexx/main/trunk/tmp'
  test -z "/opt/ooRexx/bin" || /bin/mkdir -p "/opt/ooRexx/bin"
/bin/bash ./libtool   --mode=install /usr/bin/install -c rxapi 
rexximage rexx rexxc rxqueue rxsubcom '/opt/ooRexx/bin'
  libtool: install: /usr/bin/install -c rxapi /opt/ooRexx/bin/rxapi
  libtool: install: /usr/bin/install -c .libs/rexximage 
/opt/ooRexx/bin/rexximage
  libtool: install: /usr/bin/install -c .libs/rexx /opt/ooRexx/bin/rexx
  libtool: install: /usr/bin/install -c .libs/rexxc /opt/ooRexx/bin/rexxc
  libtool: install: /usr/bin/install -c .libs/rxqueue 
/opt/ooRexx/bin/rxqueue
  libtool: install: /usr/bin/install -c .libs/rxsubcom 
/opt/ooRexx/bin/rxsubcom
  echo  is destdir
  is destdir
  echo /opt/ooRexx is prefix
  /opt/ooRexx is prefix
  echo /bin/bash /home/rony/dev/oorexx/main/trunk/install-sh -c
  /bin/bash /home/rony/dev/oorexx/main/trunk/install-sh -c
  /bin/bash /home/rony/dev/oorexx/main/trunk/install-sh -c rexx.img 
/opt/ooRexx/bin/rexx.img
  if test -z "/usr/bin/gencat"; then \
echo "No rexx.cat to install"; \
else \
/bin/bash /home/rony/dev/oorexx/main/trunk/install-sh -c 
rexx.cat /opt/ooRexx/bin/rexx.cat; \
fi
  /home/rony/dev/oorexx/main/trunk/install-sh: rexx.cat does not exist.
  make[3]: *** [install-exec-local] Error 1
  make[3]: Leaving directory `/home/rony/dev/oorexx/main/trunk/tmp'
  make[2]: *** [install-am] Error 2
  make[2]: Leaving directory `/home/rony/dev/oorexx/main/trunk/tmp'
  make[1]: *** [install-recursive] Error 1
  make[1]: Leaving directory `/home/rony/dev/oorexx/main/trunk/tmp'
  make: *** [install] Error 2
  r...@ronylinux:~/dev/oorexx/main/trunk/tmp$ 
  

What can/should I do from here on ?

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
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] V4.1

[David Ashley]

  ooRexx looks in several places for class files (as documented in the 
programming guide). I don't remember the order off the top of my head but one 
of 
the places to look is in the PATH.

David Ashley

On 08/20/2010 10:29 PM, CVBruce wrote:
> Hi,
>
> I have rexx installed in /opt/ooRexx.  In /usr/bin if have a symlink
> to /opt/ooRexx/bin/rexx.
>
> /opt/ooRexx/bin is not in my $PATH, and /opt/ooRexx/lib is not in my
> $LD_LIBRARY_PATH.
>
> In /opt/ooRexx/bin there are numerous *.cls files.
>
> I guess my question is how does ooRexx find these class files?  Should
> I put a symlink pointing from /usr/bin to /opt/ooRexx/bin/classfile.cls?
>
> Thanks for you time.
>
> Bruce
>
> --
> 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
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>


--
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
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Problems compiling 64-bit ooRexx for 64-bit Linux (Ubuntu) and installing it

[Jean-Louis Faucher]

Workaround (?) Try to configure directly from trunk, not from trunk/tmp
I remember I had problems with make install a few years ago, when
configuring from a directory different from trunk (was 32 bits).
I never tried again, so I can't tell if the problem is still there or not...


Jean-Louis
--
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
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

[Oorexx-devel] Another attempt to no avail .. (Re: Problems compiling 64-bit ooRexx for 64-bit Linux (Ubuntu) and installing it

[Rony G. Flatscher]

Hi there,

this thime I remained in "main/trunk", issued a "./configure", "make"
and then "sudo make install" with the following output:

r...@ronylinux:~/dev/oorexx/main/trunk$ sudo make install
cp ./extensions/rxregexp/rxregexp.cls ./
cp ./extensions/rxftp/rxftp.cls ./
cp ./extensions/csvStream/csvStream.cls ./
cp ./extensions/rxsock/socket.cls ./
cp ./extensions/rxsock/streamsocket.cls ./
make  install-recursive
make[1]: Entering directory `/home/rony/dev/oorexx/main/trunk'
make[2]: Entering directory `/home/rony/dev/oorexx/main/trunk'
make[3]: Entering directory `/home/rony/dev/oorexx/main/trunk'
test -z "/opt/ooRexx/bin" || /bin/mkdir -p "/opt/ooRexx/bin"
  /bin/bash ./libtool   --mode=install /usr/bin/install -c rxapi rexximage 
rexx rexxc rxqueue rxsubcom '/opt/ooRexx/bin'
libtool: install: /usr/bin/install -c rxapi /opt/ooRexx/bin/rxapi
libtool: install: warning: `librexx.la' has not been installed in 
`/opt/ooRexx/lib/ooRexx'
libtool: install: warning: `librexxapi.la' has not been installed in 
`/opt/ooRexx/lib/ooRexx'
libtool: install: /usr/bin/install -c .libs/rexximage 
/opt/ooRexx/bin/rexximage
libtool: install: warning: `librexx.la' has not been installed in 
`/opt/ooRexx/lib/ooRexx'
libtool: install: warning: `librexxapi.la' has not been installed in 
`/opt/ooRexx/lib/ooRexx'
libtool: install: /usr/bin/install -c .libs/rexx /opt/ooRexx/bin/rexx
libtool: install: warning: `librexx.la' has not been installed in 
`/opt/ooRexx/lib/ooRexx'
libtool: install: warning: `librexxapi.la' has not been installed in 
`/opt/ooRexx/lib/ooRexx'
libtool: install: /usr/bin/install -c .libs/rexxc /opt/ooRexx/bin/rexxc
libtool: install: warning: `librexx.la' has not been installed in 
`/opt/ooRexx/lib/ooRexx'
libtool: install: warning: `librexxapi.la' has not been installed in 
`/opt/ooRexx/lib/ooRexx'
libtool: install: /usr/bin/install -c .libs/rxqueue /opt/ooRexx/bin/rxqueue
libtool: install: warning: `librexx.la' has not been installed in 
`/opt/ooRexx/lib/ooRexx'
libtool: install: warning: `librexxapi.la' has not been installed in 
`/opt/ooRexx/lib/ooRexx'
libtool: install: /usr/bin/install -c .libs/rxsubcom 
/opt/ooRexx/bin/rxsubcom
echo  is destdir
is destdir
echo /opt/ooRexx is prefix
/opt/ooRexx is prefix
echo /bin/bash /home/rony/dev/oorexx/main/trunk/install-sh -c
/bin/bash /home/rony/dev/oorexx/main/trunk/install-sh -c
/bin/bash /home/rony/dev/oorexx/main/trunk/install-sh -c rexx.img 
/opt/ooRexx/bin/rexx.img
if test -z "/usr/bin/gencat"; then \
echo "No rexx.cat to install"; \
else \
/bin/bash /home/rony/dev/oorexx/main/trunk/install-sh -c 
rexx.cat /opt/ooRexx/bin/rexx.cat; \
fi
/bin/bash /home/rony/dev/oorexx/main/trunk/install-sh -c 
./platform/unix/oorexx-config /opt/ooRexx/bin/oorexx-config
/bin/bash /home/rony/dev/oorexx/main/trunk/install-sh -c 
./extensions/rxregexp/rxregexp.cls /opt/ooRexx/bin/rxregexp.cls
/bin/bash /home/rony/dev/oorexx/main/trunk/install-sh -c 
./extensions/rxftp/rxftp.cls /opt/ooRexx/bin/rxftp.cls
/bin/bash /home/rony/dev/oorexx/main/trunk/install-sh -c 
./extensions/csvStream/csvStream.cls /opt/ooRexx/bin/csvStream.cls
/bin/bash /home/rony/dev/oorexx/main/trunk/install-sh -c 
./extensions/rxsock/socket.cls /opt/ooRexx/bin/socket.cls
/bin/bash /home/rony/dev/oorexx/main/trunk/install-sh -c 
./extensions/rxsock/streamsocket.cls /opt/ooRexx/bin/streamsocket.cls
/bin/bash /home/rony/dev/oorexx/main/trunk/install-sh -c 
./extensions/rxsock/mime.cls /opt/ooRexx/bin/mime.cls
/bin/bash /home/rony/dev/oorexx/main/trunk/install-sh -c 
./extensions/rxsock/smtp.cls /opt/ooRexx/bin/smtp.cls
if test "LINUX" != "AIX" -a "LINUX" != "MACOSX"; then \
/bin/bash /home/rony/dev/oorexx/main/trunk/install-sh -c 
./rexxapi/server/platform/unix/rxapid /opt/ooRexx/bin/rxapid; \
fi
if test "LINUX" = "MACOSX"; then \
/bin/bash /home/rony/dev/oorexx/main/trunk/install-sh -c 
./platform/unix/macosx/org.rexxla.oorexx.rxapid.plist \
/opt/ooRexx/bin/org.rexxla.oorexx.rxapid.plist; \
mkdir ./platform/unix/macosx/scripts; \
sed -e "s/^VER=/VER=4/" -e "s/^REL=/REL=0/" -e "s/^MOD=/MOD=2 \
-e "s-^PREFIX=-PREFIX=/opt/ooRexx-" 
./platform/unix/macosx/postflight.in \
>./platform/unix/macosx/scripts/postflight; \
sed -e "s-^PREFIX=-PREFIX=/opt/ooRexx-" 
./platform/unix/macosx/preflight.in \
>./platform/unix/macosx/scripts/preflight; \
sed -e "s/^VER=/VER=4/" -e "s/^REL=/REL=1/" -e "s/^MOD=/MOD=0/" 
\
-e "s-^PREFIX=-PREFIX=/opt/ooRexx-" -e 
"s-^BLD_DIR=-BLD_DIR=.-" \
./platform/unix/macosx/MakeRexxPackage.in 
>./platform/unix/macosx/MakeRexxPackage; \
  

[Oorexx-devel] Request to apply patch (Re: Removing fileno()-block resolves the problem (Re: Request for help on (Ubuntu) Linux (32- and64-bit)

[Rony G. Flatscher]

Hi there,

while trying to create a 64-bit version of ooRexx for Linux, I noticed
that the enclosed patch has not yet been applied to trunk.

If the patch is o.k. as such, I would request the ooRexx team to apply it.

Reason being, that people on Ubuntu/Linux can fetch the latest ooRexx
binary from the build machine, if they wish to check out the OOo-binding
of BSF4ooRexx. Without that patch, it may not be possible for interested
people to run any OOo ooRexx scripts successfully. (Since I applied the
patch to the 32-bit ooRexx on Ubuntu no problems have occurred.)

TIA,

---rony


On 17.08.2010 15:05, Rony G. Flatscher wrote:
> Done:
>
> * bug report
>   
> 
>   containg link to the
> * patch at:
>   
> .
>
> Many thanks!
>
> ---rony
>
>
> On 17.08.2010 13:56, Rick McGuire wrote:
>> Please open a tracker for this.
>>
>> Rick
>>
>> On Tue, Aug 17, 2010 at 7:44 AM, Rony G. Flatscher
>>  wrote:
>>   
>>> Removing the fileno(handle) block in FileSystem.cpp resolves the problem!
>>> (It seems that this removal is o.k. as we received already a valid file
>>> handle at that point, which should not be the case if the maximum open file
>>> handles was exceeded already.)
>>>
>>> Shall I open a tracker with a patch for this? (Alternatively, I tried to
>>> picture the block that needs to be removed.)
>>>
>>> ---rony
>>>
>>>
>>> On 16.08.2010 20:32, Rick McGuire wrote:
>>>
>>> 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)
>>> /***/
>>> /* Function:  Read a program into a buffer */
>>> /***/
>>> {
>>> FILE*handle; /* open file access handle
>>> */
>>> size_t   buffersize; /* size of read buffer
>>> */
>>> {
>>> handle = fopen(file_name, "rb"); /* open as a binary file
>>>*/
>>> if (handle == NULL)
>>> { /* open error?   */
>>> return OREF_NULL;  /* return nothing
>>>  */
>>> }
>>>
>>> if (fileno(handle) == (FOPEN_MAX - 2))
>>> {  /* open error?   */
>>> return OREF_NULL;  /* return nothing
>>>  */
>>> }
>>>
>>> fseek(handle, 0, SEEK_END);  /* seek to the file end
>>>*/
>>> buffersize = ftell(handle);  /* get the file size
>>>*/
>>> fseek(handle, 0, SEEK_SET);  /* seek back to the file
>>> beginning   */
>>> }
>>> RexxBuffer *buffer = new_buffer(buffersize); /* get a buffer
>>> object   */
>>> ProtectedObject p(buffer);
>>> {
>>> UnsafeBlock releaser;
>>>
>>> fread(buffer->getData(), 1, buffersize, handle);
>>> fclose(handle);  /* close the file
>>>*/
>>> }
>>> return buffer;   /* return the program buffer
>>> */
>>> }
>>>
>>>
>>> I don't understand the purpose of the "fileno(handle) == (FOPEN_MAX -
>>> 2)" test, but that certainly could be the cause of this error.  It's
>>> consistent with the fact that this error occurs even if you change the
>>> name of the file.  This test appears to be something pulled forward
>>> from the 3.2.0 code, but I don't know of any reason why that should
>>> have been there in the first place.
>>>
>>> Given the number of files that the jvm generally has open, it is
>>> certainly conceivable that we're hitting a window where that's true.
>>>
>>> Rick
>>>
>>>   

--
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
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Another attempt to no avail .. (Re: Problems compiling 64-bit ooRexx for 64-bit Linux (Ubuntu) and installing it

[Jean-Louis Faucher]

If I'm not wrong, a closing quote is missing in trunk/Makefile.am
Replace
sed -e "s/^VER=/VER=$(ORX_MAJOR)/" -e "s/^REL=/REL=$(ORX_AGE)/" -e
"s/^MOD=/MOD=$(ORX_REVISION) \
by
sed -e "s/^VER=/VER=$(ORX_MAJOR)/" -e "s/^REL=/REL=$(ORX_AGE)/" -e
"s/^MOD=/MOD=$(ORX_REVISION)*/"* \

I can't test so I prefer to not commit...

Jean-Louis
--
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
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Another attempt to no avail .. (Re: Problems compiling 64-bit ooRexx for 64-bit Linux (Ubuntu) and installing it

[Rony G. Flatscher]

On 21.08.2010 22:44, Jean-Louis Faucher wrote:
> If I'm not wrong, a closing quote is missing in trunk/Makefile.am
> Replace
> sed -e "s/^VER=/VER=$(ORX_MAJOR)/" -e "s/^REL=/REL=$(ORX_AGE)/" -e
> "s/^MOD=/MOD=$(ORX_REVISION) \
> by
> sed -e "s/^VER=/VER=$(ORX_MAJOR)/" -e "s/^REL=/REL=$(ORX_AGE)/" -e
> "s/^MOD=/MOD=$(ORX_REVISION)*/"* \
>
> I can't test so I prefer to not commit...
Yes, that seems to have been it, "make install" runs successfully!

Thank you very much, indeed, Jean-Louis !

---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
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

[Oorexx-devel] For the adventurous ...

[Rony G. Flatscher]

Hi there,

it looks as if the 32-bit-Linux installer/deinstaller now work. So those
of you who are a little bit adventurous may want to take a first look at
it. Here are the necessary steps:

* create a Rexx interpreter from trunk, after applying the patch
  
,

If you have OOo installed on your system:

* Please note, the OOo-support only works with the genuine
  OpenOffice from . So, if you are
  not using gentoo, you may need to first remove the OOo supplied
  with your Linux first and install the genuine OOo afterwards.

---

Now to BSF4ooRexx:

* get
  

  and unzip to any location,
  o change into "bsf4oorexx/install/linux" and double-click on
"install.sh"

That's it.!
(Best if you logoff/logon again, but you do not have to do it.)

Whatever you notice (good or bad), please let us know.

---rony

P.S.: On 64-Bit-Ubuntu there is an issue with 64-bit-Java loading the
64-bit-so; have to look into it. Using 64-bit-Java from 64-bit ooRexx is
o.k. and one can even successfully drive genuine OOo (and e.g. run all
supplied OOo examples).

P.P.S.: Have not yet tested all the additions/changes of the Windows
installer versions, which may have little problems. Will look into that
tomorrow or Monday, as I have become far too exhausted in the past weeks
with this and need some rest...
:)
[The installation for Windows is the same, except for folder: after
unzipping change into change into "bsf4oorexx/install/windows" and
double-click on "install.cmd" and if that does not work double-click on
"install_runas_Administrator.cmd".]


--
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
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] V4.1

[CVBruce]

Thanks for the pointer, I'll check the programmer guide.

It looks like I should create the symlinks, since the current install  
process, symlinks everything else into /usr/bin.

Bruce
On Aug 21, 2010, at 1:07 PM, David Ashley wrote:

>  ooRexx looks in several places for class files (as documented in the
> programming guide). I don't remember the order off the top of my  
> head but one of
> the places to look is in the PATH.
>
> David Ashley
>
> On 08/20/2010 10:29 PM, CVBruce wrote:
>> Hi,
>>
>> I have rexx installed in /opt/ooRexx.  In /usr/bin if have a symlink
>> to /opt/ooRexx/bin/rexx.
>>
>> /opt/ooRexx/bin is not in my $PATH, and /opt/ooRexx/lib is not in my
>> $LD_LIBRARY_PATH.
>>
>> In /opt/ooRexx/bin there are numerous *.cls files.
>>
>> I guess my question is how does ooRexx find these class files?   
>> Should
>> I put a symlink pointing from /usr/bin to /opt/ooRexx/bin/ 
>> classfile.cls?
>>
>> Thanks for you time.
>>
>> Bruce
>>
>> --
>> 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
>> Oorexx-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>
>
>
> --
> 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
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel


--
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
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Another attempt to no avail .. (Re: Problems compiling 64-bit ooRexx for 64-bit Linux (Ubuntu) and installing it

[CVBruce]

Yes, I caught that, my fault.  Do an update, I corrected it a while ago.

Bruce
On Aug 21, 2010, at 1:44 PM, Jean-Louis Faucher wrote:


If I'm not wrong, a closing quote is missing in trunk/Makefile.am
Replace
sed -e "s/^VER=/VER=$(ORX_MAJOR)/" -e "s/^REL=/REL=$(ORX_AGE)/" -e  
"s/^MOD=/MOD=$(ORX_REVISION) \

by
sed -e "s/^VER=/VER=$(ORX_MAJOR)/" -e "s/^REL=/REL=$(ORX_AGE)/" -e  
"s/^MOD=/MOD=$(ORX_REVISION)/" \


I can't test so I prefer to not commit...

Jean-Louis
--
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
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel


--
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
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] For the adventurous ...

[Erico Mendonca]

>>> On 8/21/2010 at 07:19 PM, in message <4c7050fc.3060...@wu-wien.ac.at>, 
>>> "Rony G.
Flatscher"  wrote: 

> P.S.: On 64-Bit-Ubuntu there is an issue with 64-bit-Java loading the  
> 64-bit-so; have to look into it. Using 64-bit-Java from 64-bit ooRexx is o.k. 
>  
> and one can even successfully drive genuine OOo (and e.g. run all supplied  
> OOo examples). 

Rony,

In my proposed SPEC file I just placed all the libraries in /usr/lib/ooRexx, 
and added that to ld.so.conf.d. So far it's working fine under 32-bit and 
64-bit (tested under a few RPM-based distros, ran the testcases ok). Perhaps 
that would work under Ubuntu as well?




--
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
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Problems compiling 64-bit ooRexx for 64-bit Linux (Ubuntu) and installing it

[Mark Miesfeld]

On Sat, Aug 21, 2010 at 1:04 PM, Rony G. Flatscher
 wrote:

> in the need of a 64-bit ooRexx from trunk, I checked out ooRexx from
> Sourceforge.
>
> Changed into "main/trunk", created a subdir "tmp",
> ran from main/trunk/tmp the command "../conifugre --disable-static" followed
> by "make"
> then issuing a "make install" (to have it installed into /opt/ooRexx), but
> receive the following output with errors at the end:

*Don't* do make install.  *Don't* do sudo make.  If you are on a
Debian based system, Ubuntu, etc., build the the deb package.  If you
are on some other Linux, build the rpm package.

I just built on 2 different 64-bit Debian systems a couple of days
ago.  It worked fine.

Plus Jean-Louis is is sort of right, why are you creating tmp and
trying to configure from there?

Here is how you should build on a 64-bit Ubuntu, assuming a fresh
check out and no ooRexx yet installed:

# whomami
miesfeld
# svn co https://oorexx.svn.sourceforge.net/svnroot/oorexx/main/trunk main
# cd main
# ./bootstrap
# ./configure --disable-static
# make
# make deb
# cd ..
# su root
# dpkg -i oorexx_4.1.0-6128_amd64.deb

I just did that, it worked fine on Kubuntu 10.04 64-bit.  Took less
than 10 minutes, including the time spent rebooting in the Kubuntu
partition.

If, there is already an ooRexx installed, the last two step should be these 3:

# su root
# dpkg -P ooRexx
# dpgk -i ooRexx

If you already have trunk checked out, and want to be sure you have a
good build, the first step(s) should be:

# cd main
# make maintainer-clean
# svn update
# ./bootstrap
# ...

I just redid the build using the steps directly above, worked fine,
took less than 4 minutes.

--
Mark Miesfeld

--
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
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] V4.1

[Mark Miesfeld]

On Sat, Aug 21, 2010 at 4:23 PM, CVBruce  wrote:

> It looks like I should create the symlinks, since the current install
> process, symlinks everything else into /usr/bin.

Bruce,

What I would suggest doing is looking at platform/unix/oorexx.spec.in
and doing what is done in the post script.  You can locate it by
looking for the line starting with: %post

The post script is kept up to date and the rpm install is undeniably
the best tested of all the Unixes.

--
Mark Miesfeld

--
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
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel