Re: python 2.5, opensolaris and SunPro

[Carl Brewer <carl%bl.echidna.id.au@localhost>]

Roland Illig wrote:
> Carl Brewer schrieb:
> > > I prefer it if you set SUNWSPROBASE=/opt/SUNWspro instead. That will
> > > make the C++ compiler available, too.
> > Is that best set in mk.conf or an environment variable?
>
> In mk.conf. Otherwise the build environment quickly becomes inconsistent.

Noted.  As such, my mk.conf is now :



.ifdef BSD_PKG_MK       # begin pkgsrc settings

PKGSRC_COMPILER=        sunpro
SUNWSPROBASE=           /opt/SUNWspro
CC=                     /opt/SUNWspro/bin/cc

PKG_DBDIR=              /usr/pkg/.db
LOCALBASE=              /usr/pkg
VARBASE=                /usr/pkg/var
PKG_TOOLS_BIN=          /usr/pkg/sbin
PKGMANDIR=              man

TOOLS_PLATFORM.install?=        /usr/pkg/bin/install-sh
TOOLS_PLATFORM.sh?=             /usr/pkg/bin/pdksh
TOOLS_PLATFORM.ksh?=            /usr/pkg/bin/pdksh
TOOLS_PLATFORM.awk?=            /usr/pkg/bin/nawk
TOOLS_PLATFORM.sed?=            /usr/pkg/bin/nbsed
TOOLS_PLATFORM.pax?=            /usr/pkg/bin/${NBPAX_PROGRAM_PREFIX}pax
TOOLS_PLATFORM.tar?=            /usr/pkg/bin/${NBPAX_PROGRAM_PREFIX}tar

.endif                  # end pkgsrc settings




better?  Does that remove the need for any path settings or environment 
variables in the shell save for knowing where bmake is?