<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On May 28, 2013, at 4:01 PM, Martin Ward wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">i do a separate isl build so no, haven't noticed it</span></blockquote></div><br><div>Cross phase isn't a problem, I think it is in temp tools when using the cross toolchain.</div><div><br></div><div>I have an easy way to do it without adding an extra isl page to the whole book.</div><div><br></div><div>Can extract cloog-isl. Then cd to isl, configure and build and install, then after that, cd ../ and configure and use isl at /tools</div><div><br></div><div>I had no issue building cloog when not using a cross toolchain. I'm a bit burned out looking at what would be needed to get cloog to link to isl when cross compiling. I tried using LDFLAGS heh. Failed. Adding isl before cloog is a pain, with multilib, as well. Hmmmm. Decisions.</div><div><br></div><div>Sincerely,</div><div><br></div><div>William Harrington</div></body></html>