<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
No I hadn't heard of it..but..it's just another variable in this question really.<BR>
I can build gcc myself.<BR>
How to identify and implement "configurations" when "processor" and "os" don't imply the rest?<BR>
The ABIs "should" generally match, and when they do, good.<BR>
But the question still remains I think.<BR>
<BR>
One answer is "everyone just writes their own config file".<BR>
I don't like that much.<BR>
I'd like to provide pretty "constant" config files, that are slightly parameterized, via the environment or something, to handle most situations.<BR>
And to use common code.<BR>
<BR>
Probably what I'll do is have<BR>
SPARC64_SOLARIS.Common<BR>
<BR>
SPARC64_SOLARIS.GNU<BR>
C_COMPILER="GNU"<BR>
include SPARC64_SOLARIS.Common<BR>
<BR>
SPARC64_SOLARIS.SUN<BR>
C_COMPILER="Sun"<BR>
include SPARC64_SOLARIS.Common (eventually Unix.Common or just plain Common, and then a good handle on rewriting in Modula-3, but I'm not their yet..)<BR>
<BR>
and user can copy SPARC64_SOLARIS.* over SPARC64_SOLARIS, or over cm3.cfg.<BR>
Or set the M3_CONFIG environment variable.<BR>
<BR>
This is very similar to what NT386/NT386GNU/NT386MINGNU do.<BR>
<BR>
Then, with such a minimal toplevel cm3.cfg/SPARC64_SOLARIS, people can write their own.<BR>
Though the two I show should be about it.<BR>
NT386 has many more variables than other systems (possibly tied to each other, possibly not, e.g. Posixish NT386 could still use native gui, for example, and integrated backend could use X Windows and be Posixish, and gcc backend can use native gui/runtime ("mingnu"))<BR>
<BR>
Thanks,<BR>
- Jay<BR><BR><BR>> Date: Mon, 8 Sep 2008 23:37:38 +0000<BR>> From: dabenavidesd@yahoo.es<BR>> To: m3devel@elegosoft.com; jay.krell@cornell.edu<BR>> Subject: Re: [M3devel] SPARC64_SOLARIS?<BR>> <BR>> Hi Jay:<BR>> have you tried Open Sparc (gcc for sparc machines)? It seems they have binary compatibility between gcc compiled objects and gcc for sun systems, so one can try to build m3cg using gcc for sun systems and gcc. <BR>> http://cooltools.sunsource.net/gcc/<BR>> <BR>> --- El lun, 8/9/08, Jay <jay.krell@cornell.edu> escribió:<BR>> De: Jay <jay.krell@cornell.edu><BR>> Asunto: [M3devel] SPARC64_SOLARIS?<BR>> Para: "m3devel" <m3devel@elegosoft.com><BR>> Fecha: lunes, 8 septiembre, 2008 3:37<BR>> <BR>> short version:<BR>> <BR>> Basically all non-Linux, non-BSD systems have multiple toolsets -- native and<BR>> GNU.<BR>> <BR>> <BR>> There is SOLgnu and SOLsun. <BR>> There is how "NT386" encompasses multiple<BR>> configurations.<BR>> <BR>> <BR>> What should I do for SPARC64_SOLARIS?<BR>> <BR>> <BR>> medium version:<BR>> One of the nagging problems around is that of 64bit hosted m3cg consistently<BR>> not working.<BR>> While I have AMD64_LINUX and AMD64_OPENBSD setups, and I have an AMD64 Sun<BR>> machine for<BR>> AMD64_SOLARIS, the most convenient for me currently is probably<BR>> "SPARC64_SOLARIS",<BR>> for dumb reasons. "MIP64_IRIX6" might also be convenient soon,<BR>> though I think<BR>> Irix multiplies this problem out to multiple ABIs, I have to look into it<BR><BR></body>
</html>