Board index Solaris

Solaris 2.1; Is binary compat. module installed?

Solaris 2.1; Is binary compat. module installed?

Post by Devon Tu » Thu, 14 Apr 1994 02:47:11



Hello Solaris users,
     We have a customer who is running our Solaris 1.* binary application on a
Solaris 2.1 system.  They are getting a "Bad System call" message.  We are
thinking perhaps they do not have the 1.* binary compatability 'module'
installed.
     How does one tell whether they have this module installed or not?  I'm
looking for a simple way that we can use over the phone to have them check
for this.  If we can determine that they don't have 1.* compat installed,
the problem should be solved by installing it.

Thank you so much,
    Devon Tuck
    Software Engineer
    Visual Engineering  "Ovation:  PC-style Presentation Software for Unix!"

 
 
 
Top

Solaris 2.1; Is binary compat. module installed?

Post by Casper H.S. D » Thu, 14 Apr 1994 18:33:19



>Hello Solaris users,
>     We have a customer who is running our Solaris 1.* binary application on a
>Solaris 2.1 system.  They are getting a "Bad System call" message.  We are
>thinking perhaps they do not have the 1.* binary compatability 'module'
>installed.
>     How does one tell whether they have this module installed or not?  I'm
>looking for a simple way that we can use over the phone to have them check
>for this.  If we can determine that they don't have 1.* compat installed,
>the problem should be solved by installing it.

You've send them a statically linked binary, most likely.

In that case, they'll need tor un 2.3 for it to work.

If it isn't as statically linked executable, but you've linked some
system calls statically, the execuable won't work under Solaris 2.3,
because teh user mode trap0 (oldsyscall) handler only gets loaded
when the 4.1.x executable is statically linked.

Casper

 
 
 
Top

1. Solaris 2.2 binaries running on Solaris 2.1

Hello,

        We've got a package consisting of a large amount of Fortran and C.
Each program also comes in two forms; a text based version and an X windows
version. The software we use is the SPARC f77 compiler, and gcc.

        Now we're having quite horrid problems with our binaries. We try and
build them as statically as possible (ie all libraries static except libdl) so
that they should, theoretically, be as portible as possible. However the
upgrade has proved this to be a falicy. The solaris 2.1 X programs cannot
connect to your DISPLAY when ran on solaris 2.2. Similarly the same seems to
work backwards (2.2binaries (with the later hacks to get them working) on
2.1). In this latter case, linking dynamicically libsocket appears to cure
things. It seems that the 2.2 socket code does things that 2.1 does not like.

        However, even more problems abound. We cannot stick purely to dynamic
linking as that requires the fortran dynamic libraries on all systems the
software is to run on. Now here comes the oddities. Linking libF77 statically
on 2.2 and running on 2.1 causes an illegal instruction for all the X based
versions, but not the non X programs (despite the fact that our Fortran code
does no hacky calls to X). It all works hunky dorey if we dynamic link libF77,
but as I said before, this requires the SPARC compiler on 2.1 (which in our
case does exist).

        Has anyone else experienced such oddities as this? Am I to conclude
that the only solution is to have two sets of binaries - 2.1 and 2.2?

        Any help much appreciated.

                James


Medical Research Council - Laboratory of Molecular Biology,
Hills Road, Cambridge, CB2 2QH, England.

2. Starting XDM at system boot (Solaris 2.2) ??

3. rlogin can't tell who I am in Solaris 2.1

4. Partition Error

5. Solaris 2.1 printing sucks (was Re: problem with lpstat with Solaris 2.1)

6. 3com NICs -- waranty?

7. gcc binaries for Sparc Solaris 2.1. Where ????

8. Debian 2.1, APT and KDE

9. Mosaic binary for Solaris 2.1

10. binary PCNFSD for Solaris 2.1 on a 486 - Where is it?

11. Where is GCC 2.3.3 source or binary for Solaris 2.1?

12. SUMMARY: GCC binaries for Solaris 2.1 x86

13. FAQ, Intel, Solaris 2.1, gcc-2.4.5, binaries


All times are UTC
Board index