I've fixed the problems with my *.deb file for the s390x architecture.
If anyone would like it, it can be found here:
http://www.vsoft-software.com/oorexx_4.2.0-1_s390x.deb
Happy Holidays.
DJ
On 12/16/2016 02:46 PM, Jack Woehr wrote:
> Dave Jones wrote:
>>> ln: '/usr/lib/librexx.so' and
Dave Jones wrote:
>> ln: '/usr/lib/librexx.so' and '/usr/lib/librexx.so.4.0.6' are the same
maybe the args you wrote to ln are in the wrong order:
ln -s reallib symlink
is the correct order
and it should be a soft link (-s)
>>
--
Jack Woehr # "Democracy is the theory that
Have you checked that error at the top about rxapi? is rxapi in an appropriate
place? Also there should be a rxapid shell script, I think.
Bruce
> On Dec 16, 2016, at 12:07 PM, Dave Jones wrote:
>
> Hi, Jack.
>
> Yes the link is created by the post processing step
Hi, Jack.
Yes the link is created by the post processing step and isn't in the
archive itself. I'm more concerned at the moment with the actual error
the post processing steps generates "error exit
status 5".
Thanks.
DJ
On 12/16/2016 12:53 PM, Jack Woehr wrote:
> ln: '/usr/lib/librexx.so' and
ln: '/usr/lib/librexx.so' and '/usr/lib/librexx.so.4.0.6' are the same
file
Looks like the archiving process copied both the file and the link into the
archive in some fashion.
Make sure the link is not added to the archive and create the link in the
post-processing.
--
Jack Woehr
Hello, all.
I am attempting to create a ooRexx 4.2.0 .deb install file for use on a
Ubuntu 16.04 s390x system running as a guest of z/VM on an IBM z
mainframe and I have run into a problem.
I have:
1) downloaded the ooRexx-4.2.0-source.tar.gz fiel and expanded it
2) built ooRexx:
a)