<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><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="SkyDrivePlaceholder"></div>> Date: Fri, 18 May 2012 16:56:49 -0400<br>> From: hendrik@topoi.pooq.com<br>> To: m3devel@elegosoft.com<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></body>
</html>