<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>The output of autoconf/automake should have lightweight dependencies.<div>They might stress make, might require GNU make.</div><div>They might stress the sh, but I think there are adequate shells out there.</div><div><br></div><div><br></div><div>They are meant to be easy for people building stuff to use.</div><div>They aren't meant to be easy for people developing stuff to use.</div><div><br></div><div><br></div><div>Look at this way..while people complain and there are widely</div><div>used alternatives like cmake, autoconf/automake are in widespread</div><div>use, and they do provide things that work for Linux, Solaris, BSD, MacOSX, Cygwin,</div><div>HPUX, Aix, Irix, etc.</div><div></div><div><br></div><div>Furthermore, consider any platform that has a native gcc, is likely building</div><div>that with autoconf/automake.</div><div><br></div><div><br></div><div>I remain very template for "bootstrap" archives to consist of C and automake/autoconf/libtool output.</div><div>Or assembly, but still automake/autoconf -- at least to generate makefiles and decide how to run the assembler.</div><div><br></div><div><br></div><div> - Jay<br><br><br><br><br><div>> Date: Sun, 16 Aug 2015 07:27:30 +0000<br>> From: microcode@zoho.com<br>> To: m3devel@elegosoft.com<br>> Subject: Re: [M3devel] Build Server - Plan<br>> <br>> On Fri, Aug 14, 2015 at 09:22:08AM -0700, Darko Volaric wrote:<br>> > The solution for SPARC might be to create a cross-compiler. That's not<br>> > ideal but would be useful for verifying that things compile for the<br>> > platform at least, short of having the right hardware.<br>> <br>> You should have access to opencsw as Jay mentioned. If not, I can offer<br>> machine time but I can't keep the machine running all the time. Hopefully<br>> the current setup (opencsw) is still viable.<br>> <br>> > I disagree with your "only for experts" assessment. The point of this<br>> > server is that you don't have to compiler the compiler and a backend just<br>> > to get the latest (or even a properly working) compiler. That's the very<br>> > "expert" work I'm trying to automate.<br>> <br>> That is good to hear because from your list of deliverables it seemed to me<br>> there would still be a lot of tinkering to get a complete install. If you<br>> are scripting that and it can be built effortlessly and mindlessly from the<br>> deliverables then good. I think it would be ideal and very nice if people<br>> could download a turnkey tarball ready to run on their platform, or source<br>> code ready to build and an installer script that installs the final<br>> product. Jay mentioned autotools and they are usually far from optimal on<br>> Solaris because of autotools reliance on so much gnu stuff that is not<br>> always necessarily present on Solaris but that is the general idea- to be<br>> able to configure && make && make install with all the standard stuff<br>> happening like everything being installed in /usr/local/bin|lib|share and so<br>> forth.<br>> <br>> > What this system spits out is everything you need to compile anything you<br>> > want - a complete and working compiler. Not everyone wants or needs to use<br>> > all the packages. If you do, you can. Here are the instructions for doing<br>> > that: "cd <source dir>; cm3 <options>"<br>> <br>> It was probably just my unfamiliarity with the build setup and terms. I'm<br>> sorry if I wasted anybody's time with this diversion. I have been following<br>> the mailing list and it looks like Jay and Rodney are mostly discussing<br>> things with a very small number of regulars. Coming from the outside as I do<br>> I think anybody new is going to have similar questions/misunderstandings of<br>> how cm3 is built and installed, etc.<br>> <br>> > I'll be opening up the server to anyone who wants to do something<br>> > different. If someone wants to produce tarballs they can setup their own<br>> > VMs and they will get built too.<br>> <br>> Hopefully this can be integrated with what you already have running on<br>> opencsw.<br>> <br>> Thank you.<br>> <br>> <br>> _______________________________________________<br>> M3devel mailing list<br>> M3devel@elegosoft.com<br>> https://mail.elegosoft.com/cgi-bin/mailman/listinfo/m3devel<br></div></div> </div></body>
</html>