#474 S390 segmentation fault executing: ./rexx -i

3.2.0
closed
David Ashley
5
2012-08-14
2007-12-10
Anonymous
No

Trying to build ooRexx from source on a IBM System
z/Linux and getting segmentation fault whether I use
s390 (31-bit personality) or s390x (64-bit). I have
uploaded a file "ooRexx-3.2.0-1.src.rpm.out" that is
the result of the rpmbuild session.

The segmentation faultcomes after execution of
./rexx -i

System particulars:
uname -r > 2.6.5-7.283-s390x
uname -m > s390
z/Linux > SUSE Enterprise Linux 9

I tried before with "ooRexx-3.1.2-1" with the same
result.

Any pointers anyone?

Thanks.

Paul Dunkley
Email to: pdunkley AT nycers.nyc.gov
(replace " AT " with "@" before sending).

Discussion

<< < 1 2 3 (Page 3 of 3)
  • LK Swift
    LK Swift
    2008-08-06

    Logged In: YES
    user_id=2169908
    Originator: NO

    I just sent this off to the original poster, and to the developers forum:

    I managed to get this to compile using the source tarball by doing the following:
    set CFLAGS=-m31 before running configure.
    changing the Makefile so that -O2 is replaced by -O0 (zero).

    -LK Swift

     
  • Logged In: NO

    Thanks to forum poster "LK Swift" I have got a resolution to this issue of building Object
    REXX 3.2.0 on SUSE Linux 9 platform on IBM System Z. From "LK Swift"'s post he used a
    method to change the Makefile that was created and then use the source ...tar.gz file to
    do the build.

    I modified his method to use RPM to go the full way and create a RPM Package that could be
    installed, and uninstalled at will. This is what I preferred. Here is what I did, building
    on his recommendation to turn off optimazation (-O0); (Some of these steps may now be
    unnecessary but I give them all)

    1) Create a new "/etc/rpmc" file from original "/usr/lib/rpm/rpmrc". Cull the file and keep
    only the sections for a "S390" & "S390x" platform. Change the "O2" optflags parameter to
    "O0". This overrides the optimizaton parameter for RPM initiated compiles.
    2) Submit the command:

    export CFLAGS="-g -O0"

    This sets the CFLAGS on a 31-bit system. If on a 64-bit system then you will need to
    also add the "-m31" parameter to do 31-bit compiles.
    3) Run the RPM build command. From the directory where the RPM source is downloaded, do
    this:

    rpmbuild --rebuild ooRexx-3.2.0-1.src.rpm

    4) Here is the kicker; This process will bomb out telling you that directory

    /home/dashley/ad/svn/3.2.0/trunk/rpm/...

    or some variant of this, does not exist. Painstakingly recreate all the directory paths
    that it complains about. You may have to go through 4 to 5 iterations of creating
    directory paths and branches.

    If you really want a RPM package then that is the price to pay from here on. Even after
    the directories are fully in place it will still complain that it could not get a hold
    of parent directories somewhere along the line. Ignore these.

    You want to see it finally say "exit 0" at the end. When you see that then your RPM
    package will be in directory "/home/dashley/ad/svn/3.2.0/trunk/rpm/RPMS/s390/"
    as file "ooRexx-3.2.0-xxxx.s390.rpm", where xxxx is a build number it got somewhere.
    Mine was 1199.

    5) Now install like any other RPM package.

    6) Remember that you overrode the "O2" parameter for RPM compiles.You may want to reset
    it or delete the file in /etc. Up to you.

    Regards.

    Paul Dunkley
    Email to: pdunkley AT nycers.nyc.gov
    (replace " AT " with "@" before sending).

     
  • Mark Miesfeld
    Mark Miesfeld
    2009-07-08

    With ooRexx 4.0.0 David has got the rpm build to work on s390x, making this bug out of date at this time.

     
<< < 1 2 3 (Page 3 of 3)


Anonymous


Cancel   Add attachments