<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body bgcolor="#CCCCCC" text="#000000">
<p><font size="+1">Hi Kostis,</font></p>
<p><font size="+1">Thanks for your help !</font></p>
<p><font size="+1">Yes. I do understand now that my current issues are not HiPE-related. Good that someone can confirm this hypothesis I had.</font></p>
<p><font size="+1">I've found that 2 configure.in files have no knowledge of AIX > version 4, so that they use a default *) case.<br>
Patching. Re-Building...</font></p>
<p><font size="+1">Making progress ! Step by step...</font></p>
<p><font size="+1">Tony</font><br>
</p>
<br>
<div class="moz-cite-prefix">Le 16/01/2017 à 22:25, Kostis Sagonas a écrit :<br>
</div>
<blockquote cite="mid:9ee1a3ca-b0fe-e65d-6b5f-ae415c23eb52@cs.ntua.gr" type="cite">
On 01/16/2017 05:12 PM, REIX, Tony wrote: <br>
<blockquote type="cite"><br>
After building with Hipe, I've tried without Hipe. <br>
And I got the same result: an infinite loop, in read() from <br>
signal_dispatcher_thread_func(). <br>
In: ERLC ../ebin/hipe_rtl.beam with Hipe (--enable-hipe) <br>
In: ERLC ../ebin/hipe_consttab.beam without Hipe (--disable-hipe) <br>
. No idea why "hipe" appears here also. <br>
So, for now, I have a common issue, with or without hipe. <br>
</blockquote>
<br>
I can provide some info regarding the behavior you are experiencing: <br>
<br>
- Certain modules of the 'hipe' application, though not all. are compiled independently of whether HiPE is enabled or not because they are used by 'dialyzer'.
<br>
<br>
- It just so happens that 'hipe' is the first application that is compiled in the bootstrapping process, so the infinite loop you are getting is not related to HiPE but shows some deeper problem in the system you have built.
<br>
<br>
Bottomline: what you are experiencing is not HiPE-related. Your system is broken.
<br>
<br>
Kostis <br>
<br>
</blockquote>
<br>
</body>
</html>