[ksh93-integration-discuss] Re: [osol-code] Round two: ((pre-)pre-review) ksh93-integrationwebrev2007-02-02

[James Carlson]

Glenn Fowler writes:
> ksh93s built on
> SunOS hostname 5.8 Generic_108528-26 sun4u sparc SUNW,Sun-Fire-15000
> and run on
> SunOS hostname 5.6 Generic_105181-33 sun4u sparc SUNW,Ultra-2

That cannot be supported.

Building on Solaris 2.6 (5.6) and running on Solaris 8, though, is
supported.

You must always build on the oldest system you want to support.

> ksh93s built on
> SunOS hostname 5.9 Generic_118558-21 sun4u sparc SUNW,Sun-Fire-280R
> and run on
> SunOS hostname 5.6 Generic_105181-33 sun4u sparc SUNW,Ultra-2

Same thing.  We support backward compatibility, meaning that old
binaries can be run on new systems.  We don't (and can't) support it
in the other direction -- new binaries may reference system features
that didn't exist when the old system was built.

I think there's a misunderstanding here.

> now there may be some narrow path of cc/ccs flags/executables && uname -r matching
> that I could set up to make compatible binaries for all solaris
> but even then am I crippling later releases for the sake of compatibility with earlier ones?
> and I also have N-1 other target architectures with possibly
> worse version management problems,
> and finally, building a.out's is (ideally) 1% of my job
> 
> therefore, HOSTTYPE=(os)[(differentiating-number)].(architecture)[(-bits)],
> sol8.i386, sol11.i386-64 etc.

I think that's still missing the point.

This project is integrating ksh93 into ON.  Once that's done, there's
no way that the ON source will be used to build a binary for some
other release.  Having Solaris-versioning-dependent objects in the
deliverables is a syntax error.

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677