[M3devel] ports with versions in their names?

[Jay]

Tony has established consistency around ARCH_KERNEL.

 I386_DARWIN

 PPC_DARWIN

 AMD64_DARWIN

 

I followed that -- I like it and Tony said to -- but have been putting "32" in things, like:

 AMD64_FREEBSD 

 AMD64_LINUX 

 SPARC32_LINUX 

 SPARC64_LINUX  

 SPARC64_SOLARIS 

 PPC32_OPENBSD 

 I386_SOLARIS 

 MIP64_OPENBSD  

 etc.

 

I realize some platforms had it the other the other way around.

NetBSDi386v2 and a bunch in the ezm3 distribution and FSBD_ALPHA.

 

 

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.

 

 

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.

 

 

(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..)

 

 

 - Jay

 
> Date: Sat, 28 Mar 2009 11:11:50 +0100
> From: wagner at elegosoft.com
> To: jay.krell at cornell.edu
> CC: m3devel at elegosoft.com
> Subject: RE: [M3devel] ports with versions in their names?
> 
> Quoting Jay <jay.krell at cornell.edu>:
> 
> >> > I don't know if the "6" in "LINUXLIBC6" still makes sense.
> >>
> >> Perhaps just reuse the long obsolet LINUX then?
> >
> > Given {AMD64,SPARC32,SPARC64,PPC,potentially 
> > PPC64,ALPHA,ARM,SH,MIPS32,MIPS64}_LINUX, doesn't it seem wrong to 
> > use plain "LINUX"?
> >
> > I know I know most of the world hasn't seen or heard of anything 
> > besides x86.. and "64bit" means AMD64... if we just had "LINUX" and 
> > "LINUX64" hardly anyone would see a problem..
> 
> Sorry, small misunderstanding. I didn't want to omit all architecture/
> processor information, just leave out the LIBC6. So perhaps
> LINUX_MIPS32 or LINUX_AMD64 etc. would suffice?
> 
> Olaf
> -- 
> Olaf Wagner -- elego Software Solutions GmbH
> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
> phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23 45 86 95
> http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20090328/3f4fb604/attachment-0002.html>