It seems that oorexx dynamic loads its libraries from the .so symlink to the library, but these are in the oorexx-devel package. If the devel package is installed it should work. It is probably best to move the *.so links to the libs package, instead of trying to patch the code.

This problem may be a symptom of other build problems with oorexx for f15.  In particular fedora problem 427029 (The procedure SysFileTree produces wrong results) has returned with oorexx-4.1.0-3.fc14.i686, oorrexx-libs-4.1.0-3.fc15.i686, after adding oorexx-devel-4.1.0-3.fc15.i686 to circumvent the load failure.  this SysFileTree problem is also described by oorexx (http://sourceforge.net/tracker/?func=detail&atid=684730&aid=2857958&group_id=119701) as being most likely caused by a bad install with mis-matched library levels.  The solution there has been to re-install using versions from sourcforge, but as of 2011-08-31 sourceforge doesn't have any versions higher than f14.

It almost seems like not only did the symbolic links not make it into the appropriate package, but based on oorexx bug 2857958 some of the library levels used to build the packages could be suspect.

This problem is still not fixed in f17 repositories, which contain oorexx-4.1.0-4-fc17 (64-bit).  Sourceforge has a f17 version of 4.1-1-7814 which is a bug fix release, but it doesn't claim to address either of the above problems.  De-install of all oorexx 4.1.0-4 related packages obtained from Fedora repositories and downloading and installing ooRexx-4.1.1-7814.fedora17.x86_64.rpm from sourceforge resolves both problems.  

Whoever repackages this application for Fedora needs to study the packaging conventions used by sourceforge and replicate it.  Sourceforge just has a single package that contains all the required libraries and symbolic links.  The current Fedora packaging apparently separates required elements into a separate oorexx, oorexx-devel, and oorexx-libs packages without adding a dependency for oorexx-devel package to oorexx, and at the same time manages to get some of the libraries in those packages at an incompatible maintenance level!

This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping