<div dir="ltr">This appears to be a gcc bug in 4.6.3 which is the one my Ubuntu has; mgnuc seems to inherit the affliction. The suggested workaround is using -O1 to build; this works. Next error; <div><br></div><div>In file included from /usr/include/ucontext.h:27:0, from mercury_memory.c:64:/usr/include/arm-linux-gnueabihf/sys/ucontext.h:107:5: error: unknown type name ‘stack_t’make[2]: *** [mercury_memory.o] Error 1</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jun 4, 2013 at 10:26 AM, Tycho Luyben <span dir="ltr"><<a href="mailto:tycho@e-lab.nl" target="_blank">tycho@e-lab.nl</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Make seems to succeed, but when running make install, I get this: <div><br></div><div>In file included from mercury_deep_copy.c:59:0:mercury_deep_copy_body.h: In function ‘MR_deep_copy’:mercury_deep_copy_body.h:850:1: error: unable to find a register to spill in class ‘LO_REGS’mercury_deep_copy_body.h:850:1: error: this is the insn:(insn 399 402 400 41 (set (mem:SI (plus:SI (reg/f:SI 13 sp) (const_int 4 [0x4])) [0 S4 A32]) (reg/v/f:SI 945 [orig:622 lower_limit ] [622])) mercury_deep_copy_body.h:345 637 {*thumb2_movsi_vfp} (nil))mercury_deep_copy_body.h:850: confused by earlier errors, bailing outPreprocessed source stored into /tmp/ccExTTfj.out file, please attach this to your bugreport.make[2]: *** [mercury_deep_copy.o] Error 1</div>
</div><div class="gmail_extra"><div><div class="h5"><br><br><div class="gmail_quote">On Mon, Jun 3, 2013 at 6:37 PM, Julien Fischer <span dir="ltr"><<a href="mailto:jfischer@opturion.com" target="_blank">jfischer@opturion.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><br>
<br>
On Mon, 3 Jun 2013, Tycho Luyben wrote:<br>
<br>
</div><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Ah that sounds great! I should not do the github then but the zip?<br>
</blockquote>
<br></div>
No, you should grab a source tarballs from our download site:<br>
<<a href="http://dl.mercurylang.org/index.html" target="_blank">http://dl.mercurylang.org/<u></u>index.html</a>>.<br>
<br>
The archives generated by github will not contain the pre-generated<br>
C files.<br>
<br>
Cheers,<br>
Julien.<div><div><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Jun 3, 2013 4:53 PM, "Julien Fischer" <<a href="mailto:jfischer@opturion.com" target="_blank">jfischer@opturion.com</a>> wrote:<br>
<br>
Hi again,<br>
<br>
On Mon, 3 Jun 2013, Tycho Luyben wrote:<br>
<br>
Is it possible to get Mercury working on ARM? I cannot find any<br>
references to it, except from 2005 which is outdated. It seems because<br>
of the C generation, it should be capable of compiling the compiler to<br>
ARM from an Intel machine using a cross compiler? And then (if needed)<br>
bootstrap with that? Any issues with that ? Did anyone do that?<br>
<br>
<br>
I should have read the last part of that a little more carefully.<br>
You don't need a Mercury compiler to bootstrap the compiler.<br>
The Mercury source distribution contains pre-generated C files, so<br>
you should be able to boostrap the compiler with just a C compiler.<br>
(Given the appropriate build tools, e.g. make etc, you should just<br>
be able to compile it directly on your ARM machine.)<br>
<br>
Cheers,<br>
Julien.<br>
<br>
<br>
<br>
</blockquote>
</div></div></blockquote></div><br><br clear="all"><div><br></div></div></div><div class="im">-- <br><div><font color="#0000ff" face="Arial" size="1"><br></font></div><font color="#0000ff" face="Arial" size="1"><div><font color="#0000ff" face="Arial" size="1"><br>
</font></div>Op de inhoud van deze e-mail en op alle diensten en producten van en onder E-lab BV of E-lab BV websites en werk namen zijn onze <a href="http://e-lab.nl/Voorwaarden.rtf" target="_blank">algemene voorwaarden</a> van toepassing. Aan de inhoud van de email en bijlagen kunnen geen rechten worden ontleend. </font><div>
<font color="#0000ff" face="Arial" size="1"><br></font></div><div><font color="#0000ff" face="Arial" size="1">The content of this e-mail as well as all services and products of E-lab BV fall under our terms of service. No rights may be derived from the content or attachments of this message.</font></div>
</div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div><font color="#0000ff" face="Arial" size="1"><br></font></div><font color="#0000ff" face="Arial" size="1"><div><font color="#0000ff" face="Arial" size="1"><br>
</font></div>Op de inhoud van deze e-mail en op alle diensten en producten van en onder E-lab BV of E-lab BV websites en werk namen zijn onze <a href="http://e-lab.nl/Voorwaarden.rtf" target="_blank">algemene voorwaarden</a> van toepassing. Aan de inhoud van de email en bijlagen kunnen geen rechten worden ontleend. </font><div>
<font color="#0000ff" face="Arial" size="1"><br></font></div><div><font color="#0000ff" face="Arial" size="1">The content of this e-mail as well as all services and products of E-lab BV fall under our terms of service. No rights may be derived from the content or attachments of this message.</font></div>
</div>