SB 2500 vs SB1000
in [Solaris]
|
Prev: Help on resetting root password in Cyclade for Solaris servers***Beginner Question***
Next: cannot open neither boot_archive nor miniroot jumpstart
From: Stuart on 23 Mar 2010 20:07 I have what is probably a dumb question. Can a code compiled on an SB using the SUN Forte compiler actually run on a SB2500 if that compiler is installed on the SB2500? In other words, is recompiling needed or will it work (maybe not as efficiently) without? Stuart
From: Doug McIntyre on 23 Mar 2010 21:59 Stuart <bigdakine(a)aol.com> writes: > I have what is probably a dumb question. >Can a code compiled on an SB using the SUN Forte compiler actually run >on a SB2500 if that compiler is installed on the SB2500? >In other words, is recompiling needed or will it work (maybe not as >efficiently) without? If you compile code on a SPARC system, it'll be to an executable, which you should be able to deploy just the executable (and any dynamic libs it depends on) onto any SPARC box with the same OS revision or newer than what you compiled on (but not older rev of OS). You shouldn't need to compile it again when moving it from SPARC system to SPARC system. If you wanted to move it to an x86 system, then, it would require a recompile (and possibly deal with any code endian depency bugs in the code).
From: Stuart on 23 Mar 2010 23:13 On Mar 23, 3:59 pm, Doug McIntyre <mer...(a)geeks.org> wrote: > Stuart <bigdak...(a)aol.com> writes: > > I have what is probably a dumb question. > >Can a code compiled on an SB using the SUN Forte compiler actually run > >on a SB2500 if that compiler is installed on the SB2500? > >In other words, is recompiling needed or will it work (maybe not as > >efficiently) without? > > If you compile code on a SPARC system, it'll be to an executable, > which you should be able to deploy just the executable (and any > dynamic libs it depends on) onto any SPARC box with the same OS > revision or newer than what you compiled on (but not older rev of OS). > > You shouldn't need to compile it again when moving it from SPARC > system to SPARC system. If you wanted to move it to an x86 system, > then, it would require a recompile (and possibly deal with any code > endian depency bugs in the code). OK. Thats what I thought. Stuart
From: Chris Ridd on 24 Mar 2010 02:33 On 2010-03-24 01:59:13 +0000, Doug McIntyre said: > Stuart <bigdakine(a)aol.com> writes: >> I have what is probably a dumb question. > >> Can a code compiled on an SB using the SUN Forte compiler actually run >> on a SB2500 if that compiler is installed on the SB2500? > >> In other words, is recompiling needed or will it work (maybe not as >> efficiently) without? > > If you compile code on a SPARC system, it'll be to an executable, > which you should be able to deploy just the executable (and any > dynamic libs it depends on) onto any SPARC box with the same OS > revision or newer than what you compiled on (but not older rev of OS). > > You shouldn't need to compile it again when moving it from SPARC > system to SPARC system. If you wanted to move it to an x86 system, > then, it would require a recompile (and possibly deal with any code > endian depency bugs in the code). You can also pass the compiler flags to make it optimize the code to only run on particular model CPUs. I couldn't find a Forte manual so the options might have changed a bit, but there's a table in the Studio 11 manual which shows what works/doesn't work: <http://docs.sun.com/source/819-3688/cc_ops.app.html#pgfId-1000197> You shouldn't need the compiler installed on the SB2500 just to run binaries built on the original box. -- Chris
From: Paul Floyd on 24 Mar 2010 16:08
["Followup-To:" header set to comp.unix.solaris.] On Tue, 23 Mar 2010 17:07:27 -0700 (PDT), Stuart <bigdakine(a)aol.com> wrote: > > I have what is probably a dumb question. > > Can a code compiled on an SB using the SUN Forte compiler actually run That's Sun Studio (and it has been for something like 7 years now). > on a SB2500 if that compiler is installed on the SB2500? You don't need to install the compiler on the target machine. The target machine should have the same (or higher) version of Solaris, and the same (or higher) level of patched (in particular, stuff like libc). You might have to compile wiht generic options rather than options for a specific chip, but otherwise it should all work. A bientot Paul -- Paul Floyd http://paulf.free.fr |