<html><body bgcolor="#FFFFFF"><div>No no no.</div><div>We will not have an explosion of targets like this. We hopefully will have a drastic reduction.</div><div>Processor: C or C++</div><div>Threads: pthreads or Win32 or maybe ucontext or setjmp</div><div>GUI: X Windows or Win32 or none or maybe other</div><div>Suspension: cooperative and probably no other</div><div><br></div><div><br></div><div>If the right level of #ifdef and/or autoconf and/or libtool use can makes its way into the "object code", maybe just target completely. (imagine one C source distribution for ALL targets and what that requires).</div><div>We have rather replaced autoconf & libtool with our carefully researched & written quake code, for better & worse & I am torn as to if this is a good thing. Autoconf & libtool are slow & obscure but ubiquitous, get the job done, are actively maintained by others.</div><div><br></div><div><br> - Jay (briefly/pocket-sized-computer-aka-phone)</div><div><br>On May 19, 2012, at 11:32 AM, "Daniel Alejandro Benavides D." <<a href="mailto:dabenavidesd@yahoo.es">dabenavidesd@yahoo.es</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div><table cellspacing="0" cellpadding="0" border="0"><tbody><tr><td valign="top" style="font: inherit;">Hi all:<br>
I would want LINUX_I80_8Y or if you prefer LINUX_I_8Y,<br>
for instance to allow and or LINUX_I8086, etc LINUX_I387 <br>
For VAXen computers:<br>
VMS_VAX__<br>
for VAX Mini/Mainframe VMS_VAX9K or VMS_VAX11<br>
Alpha's: OSF_ALPHA<br>
For Unixes:<br>
FBSD-GENERIC_I_86___--<br>
To allow: FBSD-2_I386.MAX, OBSD-6_I_86.AMD64<br>
Also could be managed by Manufacturer Model code-name, like<br>
DEC_AQUARIUS or DEC_10000.<br>
<br>
Also if we are gonna take macro assembly for cross-platform distributions then, we would need something akin:<br>
NT_XASM-I_86___<br>
So to cross-assembly from C-RT to POSIX interoperability NT-I_86GNU (if such is supported in any appropriate version, Jay)<br><br>This would allow to compile CVSup at least is what one would like to<br>Thanks in advance<br><br> --- El <b>vie, 18/5/12, Jay K <i><<a href="mailto:jay.krell@cornell.edu">jay.krell@cornell.edu</a>></i></b> escribió:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>De: Jay K <<a href="mailto:jay.krell@cornell.edu">jay.krell@cornell.edu</a>><br>Asunto: Re: [M3devel] more Debian packages?<br>Para: <a href="mailto:hendrik@topoi.pooq.com">hendrik@topoi.pooq.com</a>, "m3devel" <<a href="mailto:m3devel@elegosoft.com">m3devel@elegosoft.com</a>><br>Fecha: viernes, 18 de mayo, 2012 16:50<br><br><div id="yiv1490191613">
<style><!--
#yiv1490191613 .yiv1490191613hmmessage P
{
margin:0px;padding:0px;}
#yiv1490191613 body.yiv1490191613hmmessage
{
font-size:10pt;font-family:Tahoma;}
--></style><div><div dir="ltr">
Yes and yes.<br>LINUXLIBC6 and AMD64_LINUX can coexist -- different targets can coexist.<br>But "squeeze" vs. "wheezy" will both just be LINUXLIBC6.<br> <br> <br>Please try to use I386_LINUX.<br>I really want to stop this LINUXLIBC6 stuff...<br> <br> <br> You can share the source.<br> But we also have outputs in the source tree (unfortunately!).<br> You see -- Modula-3 build system ahead of its time at the time in putting each package's output separate from the source, but that is now not uncommon, and Modula-3 then falls down because at least by default, a multi-package source tree contains its outputs... Modula-3 does things better than most folks at the time, and now worse than everyone knows is ideal and that some folks do...<br> <br> <br> Do this to switch:<br> <br> ./do-cm3-all.py realclean <br> <br> - Jay<br> <br><div><div id="yiv1490191613SkyDrivePlaceholder"></div>> Date: Fri, 18 May 2012 16:56:49 -0400<br>> From: <a href="mailto:hendrik@topoi.pooq.com"><a href="mailto:hendrik@topoi.pooq.com">hendrik@topoi.pooq.com</a></a><br>> To: <a href="mailto:m3devel@elegosoft.com"><a href="mailto:m3devel@elegosoft.com">m3devel@elegosoft.com</a></a><br>> Subject: [M3devel] more Debian packages?<br>> <br>> Having succeeded at producing a binary .deb packages for Debian squeeze <br>> (though I still have to try it out), I'm now looking at my other <br>> machines. I have a 32-bit Intel machine with wheeze (testing), and one <br>> that can run squeeze (stable). All of them have access to the same <br>> NFS-mounted source tree. Is it practical to use the same tree for two <br>> different platforms (such as AMD64_LINUX and LINUXLIB6?) and will they <br>> be kept separate? Or do I need to clean it out or copy it?<br>> <br>> (by the way, I expect making packages for different Debian releases on <br>> the same hardware architecture will require a new source tree, or a <br>> cleaned-out one. In my case they'll
both be LINUXLIBC6)<br>> <br>> -- hendrik<br>> <br></div> </div></div>
</div></blockquote></td></tr></tbody></table></div></blockquote></body></html>