[M3devel] Couple of CM3 build comments (Solaris/SPARC).

[Tony Hosking]

Yes, those are because your m3cc backend is configured to us GNU as,  
so it is just a matter of making sure your cm3.cfg uses the same  
assembler.  In general, these problems are difficult to reconcile.  I  
suspect we want SOLgnu to assume a full GNU toolchain and SOLsun to  
assume no GNU toolchain, but in many instances systems are configured  
as some hybrid of the two.  For example, my gcc installation on  
Solaris is configured to use /usr/ccs/bin/as, and I don't have GNU ld  
installed either -- hence the definitions in my cm3.cfg.

On Aug 21, 2007, at 10:21 AM, Alex Bochannek wrote:

> Tony Hosking <hosking at cs.purdue.edu> writes:
>
>>> o Ran into another problem with as and for some reason Tony's  
>>> cm3.cfg
>>>   used /usr/ccs/bin/as, which chokes on the GNU as directives.  
>>> Changed
>>>   cm3.cfg again.
>>
>> Which file chokes?  Is it because your m3cc is configured to use  
>> GNU as?
>
> I get these kinds of errors:
>
> /usr/ccs/bin/as: "RTHeapMap.ms", line 1558: error: unknown opcode  
> ".subsection"
> /usr/ccs/bin/as: "RTHeapMap.ms", line 1558: error: statement syntax
> /usr/ccs/bin/as: "RTHeapMap.ms", line 1619: error: unknown opcode  
> ".previous"
> /usr/ccs/bin/as: "RTHeapMap.ms", line 1619: error: statement syntax
>
> for RTHeapMap, RTTipe, RTTypeMap, RTExStack, and Poly when I run
> do-cm3-core buildship.
>
>>> o do-cm3-core.sh completed and I did an install-cm3-compiler.sh
>>> upgrade,
>>>   again as root since it's writing it into /usr/local/cm3
>>>
>>> o Finally, did a do-cm3-std.sh buildship, which ran for quite a  
>>> while.
>>>
>>> o Ran into compile problems with Gdb (looked like a C99 issue, but I
>>>   didn't investigate it further. Just ran a cm3 in m3gdb again  
>>> and the
>>>   error is below.)
>>>
>>> o Commented out m3gdb in def-std-pkgs.sh and did a do-cm3-std.sh
>>>   buildship again.
>>>
>>> o The compile and install succeeded and I now have a nice new
>>>   cm3-d5.5.0.
>>>
>>> o Compiler some stuff in m3-games, just to make sure it really works
>>> and
>>>   it looks like I am OK for now. I do see a number of core dumps
>>> though
>>>   with some of apps, but I am not going to debug that at this point.
>>
>> What's core dumping?  Is this from before my fixes to thread stopping
>> yesterday?
>
> I just ran into problems with a couple of things out of m3-demo and
> m3-games. Don't recall what it was (although Juno won't run right  
> now),
> but I will do a CVS update and build a new system and report back if
> something doesn't work.
>
> Alex.