<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Tony has established consistency around ARCH_KERNEL.<BR>
I386_DARWIN<BR>
PPC_DARWIN<BR>
AMD64_DARWIN<BR>
<BR>
I followed that -- I like it and Tony said to -- but have been putting "32" in things, like:<BR>
AMD64_FREEBSD <BR>
AMD64_LINUX <BR>
SPARC32_LINUX <BR>
SPARC64_LINUX <BR>
SPARC64_SOLARIS <BR>
PPC32_OPENBSD <BR>
I386_SOLARIS <BR>
MIP64_OPENBSD <BR>
etc.<BR>
<BR>
I realize some platforms had it the other the other way around.<BR>
NetBSDi386v2 and a bunch in the ezm3 distribution and FSBD_ALPHA.<BR>
<BR>
<BR>
But, I carefully only asked about platforms with versions in their names, which are clearly dubious, not about the more general issue of naming stuff.<BR>
<BR>
<BR>
If Linux is "permanently" on libc 6.x, like the kernel is permanently 2.6.x, then my question/argument holds less/no water -- that's why I stated that way and made it "stronger" "against" NetBSD and FreeBSD, where I know the version history much better.<BR>
<BR>
<BR>
(I understand, I think, part of the history. I think Linux had its own C runtime, and that got up to around version 5.x. And then there was a big switch to glibc, since that came after "linux libc 5.x", natural to call it 6. Though in reality I think the glibc version is 2.x..maybe it should have been called LINUXGLIBC..? It is mostly moot now, that's not likely to be a name introduced at this point..though there are currently multiple viable C runtimes on Linux -- uclibc, newlib, dietlibc..)<BR>
<BR>
<BR>
- Jay<BR><BR> <BR>> Date: Sat, 28 Mar 2009 11:11:50 +0100<BR>> From: wagner@elegosoft.com<BR>> To: jay.krell@cornell.edu<BR>> CC: m3devel@elegosoft.com<BR>> Subject: RE: [M3devel] ports with versions in their names?<BR>> <BR>> Quoting Jay <jay.krell@cornell.edu>:<BR>> <BR>> >> > I don't know if the "6" in "LINUXLIBC6" still makes sense.<BR>> >><BR>> >> Perhaps just reuse the long obsolet LINUX then?<BR>> ><BR>> > Given {AMD64,SPARC32,SPARC64,PPC,potentially <BR>> > PPC64,ALPHA,ARM,SH,MIPS32,MIPS64}_LINUX, doesn't it seem wrong to <BR>> > use plain "LINUX"?<BR>> ><BR>> > I know I know most of the world hasn't seen or heard of anything <BR>> > besides x86.. and "64bit" means AMD64... if we just had "LINUX" and <BR>> > "LINUX64" hardly anyone would see a problem..<BR>> <BR>> Sorry, small misunderstanding. I didn't want to omit all architecture/<BR>> processor information, just leave out the LIBC6. So perhaps<BR>> LINUX_MIPS32 or LINUX_AMD64 etc. would suffice?<BR>> <BR>> Olaf<BR>> -- <BR>> Olaf Wagner -- elego Software Solutions GmbH<BR>> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany<BR>> phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23 45 86 95<BR>> http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin<BR>> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194<BR>> <BR></body>
</html>