[M3devel] AMD64_LINUX; duplicate Uucontext.i3 in m3core/src/unix/...; cm3-min...; various

[Jay]

That's very reasonable. You could just commit that imho.
 
 
More general and reasonable would be:
 
 
> + readonly LIB_INSTALL = INSTALL_ROOT & SL & "lib" & WORD_SIZE & PROFILING_P % libraries

or even
 
> + readonly LIB_INSTALL = INSTALL_ROOT & SL & "lib/" & TARGET & PROFILING_P % libraries

 
though granted, most systems aren't biarch/multiarch, so what you have is maybe best, possibly manually adding in biarch/multiarch systems as they are discovered -- e.g. most but not all x86 systems. (This area is actually "surprisingly large" Irix has two 32bit ABIs, there are 32bit ABIs for IA64, I think like on HP-UX).
 
 
The full lib/TARGET helps for NT386 vs. NT386GNU.

 - Jay


----------------------------------------
> Subject: RE: [M3devel] AMD64_LINUX; duplicate Uucontext.i3 in m3core/src/unix/...; cm3-min...; various
> From: dragisha at m3w.org
> To: jay.krell at cornell.edu
> CC: m3devel at elegosoft.com
> Date: Fri, 30 Jan 2009 22:33:16 +0100
>
> What remains as a problem is /lib vs. /lib64 thing.
>
> I've done this by applying this:
>
> @@ -37,9 +37,13 @@
>
> %------------------------------------------------------------------------------
>
> readonly BIN_INSTALL = INSTALL_ROOT & SL & "bin" % executables
> -readonly LIB_INSTALL = INSTALL_ROOT & SL & "lib" & PROFILING_P % libraries
> +if equal(TARGET, "AMD64_LINUX")
> + readonly LIB_INSTALL = INSTALL_ROOT & SL & "lib64" & PROFILING_P % libraries
> +else
> + readonly LIB_INSTALL = INSTALL_ROOT & SL & "lib" & PROFILING_P % libraries
> +end
> readonly PKG_INSTALL = INSTALL_ROOT & SL & "pkg" % packages
> readonly DOC_INSTALL = INSTALL_ROOT & SL & "doc" % documents
>
>
> This way I can choose which development to use, while maintaining both
> runtimes on-system. LINUXLIBC6 and AMD64_LINUX separation will work for
> pkg, but folder containing links - $INSTALLROOT + SL + "lib" on
> AMD64_LINUX must use lib64.
>
> On Fri, 2009-01-30 at 15:37 +0000, Jay wrote:
>> The alternate naming and lack of cminstall is mostly deliberate.
>>
>> The "posix" in "amd64 linux posix" is redundant. I just call it "amd64 linux". Deliberate.
>>
>> The lack of a timestamp is due to "not yet implemented". (Thus "mostly" deliberate.)
>>
>> cminstall isn't needed. Deliberate.
>>
>> You just extract the archive and set $PATH.
>> The cm3.cfg file in the archive should just work.
>> If it doesn't, please let me know.
>>
>>
>> All the releases I make and upload are like this, including the LINUXLIBC6 ones.
>>
>>
>> The Uucontext.i3 problem should be fixed now.
>>
>> - Jay
>>
>> ----------------------------------------
>>> From: dragisha at m3w.org
>>> To: m3devel at elegosoft.com
>>> Date: Fri, 30 Jan 2009 15:35:45 +0100
>>> Subject: [M3devel] AMD64_LINUX; duplicate Uucontext.i3 in m3core/src/unix/...; cm3-min...; various
>>>
>>> As I can see, structure and naming of cm3-min archive for AMD64_LINUX is
>>> not consistent with LINUXLIBC6 one... And there is no cminstall
>>> inside... What to do?
>>>
>>> What am I supposed to do with these two per configuration?
>>>
>>> m3core/src/unix% grep Uucon **/m3m*
>>> Common/m3makefile: Interface("Uucontext")
>>> darwin-amd64/m3makefile:Interface ("Uucontext")
>>> darwin-i386/m3makefile:Interface ("Uucontext")
>>> darwin-ppc/m3makefile:Interface ("Uucontext")
>>> freebsd-4/m3makefile:Interface ("Uucontext")
>>> linux-64/m3makefile:Interface ("Uucontext")
>>> linux-i386/m3makefile:Interface("Uucontext")
>>> solaris-2-x/m3makefile:Interface ("Uucontext")
>>>
>>> I've added my cm3.spec to archive and built binaries for LINUXLIBC6
>>> without problem... Same day I tried AMD64_LINUX through analog process
>>> and - build fails. Anybody had success with AMD64_LINUX build in recent
>>> CVS heads?
>>>
>>> TIA,
>>>
>>> --
>>> Dragiša Durić
>>>
> --
> Dragiša Durić 
>