[M3devel] Build Server - Plan

[microcode at zoho.com]

On Sun, Aug 16, 2015 at 10:04:29AM +0000, Jay K wrote:
> It is like you thought:The SOLsun build used the Sun C compiler, and
> probably assembler and linker.The SOLgnu build used the GNU C compiler, and
> maybe assembler, and maybe linker.It isn't a big deal. Turnkey is based on
> what people have installed.

Are you saying now that you have consolidated the builds into the 4 you
listed below they will use what the user has installed? If so that sounds
ideal, except for possible search order issues. The gcc that "comes with"
Solaris is always installed in the same location (/usr/sfw) but the path to
Studio depends on the version and I believe you could create non-standard
paths using the tarball installers vs. the package installers (Studio offers
both options IIRC). And then there is what the user has in their PATH which
might be all, one, or none of the above. And there are some users who
install new(er) versions of gcc, usually in addition to the stock version
and there is no convention for where this gcc should go.

So...there should probably be a documented way to use the toolchain of your
choice, if this isn't already explained somewhere.

> I don't know how to acquire/install the Sun compilers. 

They are a free download from Oracle (free to use and free runtime). If they
are not already installed on your opencsw box(es) and you would like to have
them on there I can do that. It is just a matter of downloading and
installing the packages. It should take 20 to 30 minutes.

> Also,"SOL" is SPARC32_SOLARIS.We now have SPARC64_SOLARIS, I386_SOLARIS,
> AMD64_SOLARIS.I didn't want to double up those also.Arguably we don't need
> configurations..just a collection of factors. 

I think this is the right thing to do, I just don't understand how to select
which toolchain you want to use, and further, I thought the downloads
contained a prebuilt cm3, so I don't understand why a C toolchain would be
required at all, unless you are saying in the future the user will compile
cm3 rather than get a prebuilt binary.


>  - Jay
> 
> 
> > Date: Sun, 16 Aug 2015 07:16:08 +0000
> > From: microcode at zoho.com
> > To: m3devel at elegosoft.com
> > Subject: Re: [M3devel] Build Server - Plan
> > 
> > On Fri, Aug 14, 2015 at 07:24:54PM +0000, Jay K wrote:
> > >  >  people are in a consolidating mood it might be good to > just use the Solaris Studio version instead of gcc on that platform.
> > > I already mostly solved this years ago.
> > 
> > Oh, that is good news.
> > 
> > > SOLgnu and SOLsun were always already the same, e.g. same threading,same
> > > jmpbuf, except the config files picked a different C compiler and
> > > differentoutput directory name. 
> > 
> > I had misunderstood there was a choice because of the download names,
> > suggesting you actually got a compiler built with Studio or gcc depending on
> > which file you downloaded.
> > 
> > > The "new" target names are SPARC32_SOLARIS, SPARC64_SOLARIS, and
> > > I386_SOLARIS,AMD64_SOLARIS. In the config files you can pick GNU or Sun
> > > compiler.I invented a separate variable with better granularity. 
> > 
> > That sounds much better, thanks. But for the downloadable stuff where
> > presumably you get a working setup already built and just have to untar the
> > tarball, which compiler(s) are you going forward with now? In other words,
> > since you have consolidate the various Solaris versions as you listed above
> > and it is no longer necessarily indicative of Studio v. gcc, are you going
> > to make turnkey builds available as in the past and if so what will they be
> > built with? And I would vote for using Studio if possible...
> > 
> > Thanks.
> > 
> > _______________________________________________
> > M3devel mailing list
> > M3devel at elegosoft.com
> > https://mail.elegosoft.com/cgi-bin/mailman/listinfo/m3devel
>  		 	   		  

--