#144 lt-rexx seg violation during amd64 install

[Anonymous]

I'm trying to install oorexx-3.0.0 on an amd64 system
runing RHEL WS v3 (kernel 2.4.21-15.0.2). I'm starting
with the source code (oorexx-3.0.0.tar.gz) I just
downloaded. After unpacking and running configure, the
build process starts without problem. At some point,
the script file 'rexx' is called, which then tries to
issue a call to ".libs/lt-rexx -i", which results in a
segment violation.

A couple of points:

1) I can issue the command ".libs/lt-rexx" without any
argument and it runs OK

"Syntax is "rexx [-v] filename [arguments]"

2) I erased all files and unpacked the source again,
but this time I didn't run configure. I noticed
that the file .libs/lt-rexx was part of the base
package; i.e. it isn't built as part of the build
process. I also noticed that file reports it as

ELF 64-bit LSB executable, AMD x86-64

So I assume this is an amd64 specific file (I ran a
similar install on an ia32 system without problem; I
assume because it didn't/couldn't run lt-rexx).
Just running lt-rexx 'out of the box' still results
in the violation, so it apparently ships that way.

I can you send you the core file upon request.

[Nobody/Anonymous]

Logged In: NO

Submitted by Kenneth Kahn
kenkahn@cadence.com
Cadence Design Systems

[Rick McGuire]

Logged In: YES
user_id=1125291

The existing ooRexx code can NOT be built as a 64-bit
executable on any system currently. The next major release
(4.0) will be cleaned up so it can function on a 64-bit
system, but there's no estimated timeframe for availability
of that release currently.

[Martin Krischik]

Logged In: YES
user_id=697486
Originator: NO

It's now 1 3/4 years later and 4.0 / 64 bit support is still no where to be seen. And by now it is almost impossible to buy a 32bit computer. Personally I think this problem should not be closed but top priority.