SCO 5.0.6 binaries stopped working on 5.0.7 MP5 - SCO

This is a discussion on SCO 5.0.6 binaries stopped working on 5.0.7 MP5 - SCO ; Anyone have any idea why binaries compiled with GCC 3.3.1 on SCO OpenServer 5.0.6 (w/o execution environment update) would suddenly stop working on OpenServer 5.0.7 with MP5? Prior to MP5, everything worked as expected. The only problem appears to be ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: SCO 5.0.6 binaries stopped working on 5.0.7 MP5

  1. SCO 5.0.6 binaries stopped working on 5.0.7 MP5

    Anyone have any idea why binaries compiled with GCC 3.3.1
    on SCO OpenServer 5.0.6 (w/o execution environment update)
    would suddenly stop working on OpenServer 5.0.7 with MP5?

    Prior to MP5, everything worked as expected. The only
    problem appears to be with dynamically loading shared
    objects (dlopen()). The error received is something like
    this:

    "OpenServer executable cannot load UDK shared object"

    Please note I receive this same error when trying to run
    on SCO OpenServer 6, so it seems like they backported
    this issue from SCO6 ... nice...

    -Brad

  2. Re: SCO 5.0.6 binaries stopped working on 5.0.7 MP5

    > Anyone have any idea why binaries compiled with GCC 3.3.1
    > on SCO OpenServer 5.0.6 (w/o execution environment update)
    > would suddenly stop working on OpenServer 5.0.7 with MP5?
    >
    > Prior to MP5, everything worked as expected. The only
    > problem appears to be with dynamically loading shared
    > objects (dlopen()). The error received is something like
    > this:
    >
    > "OpenServer executable cannot load UDK shared object"
    >
    > Please note I receive this same error when trying to run
    > on SCO OpenServer 6, so it seems like they backported
    > this issue from SCO6 ... nice...


    If anyone is interested, this is actually a GCC issue.
    GCC 3.4.6 on SCO 5.0.7 MP5 also produces the same issue.

    The work-around is to run
    /udk/usr/ccs/bin/elfmark -t osr5 ${so_file}
    to correct the issue, as apparently the shared objects
    get marked wrong and 5.0.7MP5 has a sanity check which
    prior releases didn't have, preventing the load.

    -Brad

+ Reply to Thread