Hi, Robert<div><br></div><div>I agree with you that mercury compiler compilation is too slow. I remember when I tried to build it from sources on my AMD 3000+ Ghz 2 Gb box it took nearly 4-5 hours.</div><div><br></div><div>
However if you are a Windows user, you can get already compiled binaries of mercury from</div><div><br></div><div><a href="http://code.google.com/p/winmercury/" target="_blank">http://code.google.com/p/winmercury/</a></div>
<div><br></div>
<div><br></div><div><a href="http://code.google.com/p/winmercury/" target="_blank"></a>Sincerely yours,</div><div>Vladimir<br><br><div class="gmail_quote">On Wed, Oct 13, 2010 at 5:23 PM, Robert Shiplett <span dir="ltr"><<a href="mailto:grshiplett@gmail.com" target="_blank">grshiplett@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I hope I am not the first non-academic user to ask merc-dev's that the<br>
likely size of HD required be indicated at least to an order of mag<br>
<br>
Having never spent so many hours and CPU cycles just to get a compiler<br>
+ libraries to build for a language which I only propose to use (as<br>
opposed to requested, suggested or required to use by a client or<br>
manager), it was intensely frustrating to have what finally appeared<br>
to be a succesful install run simply fail at 3 am ( I awoke due to<br>
the HD silence ) with a lack of space.<br>
<br>
While many new machines have 2 250Gb drives, my old XP box has added<br>
Firewire devices as needed: and with a new contract I will have more<br>
space.<br>
<br>
But just as I now live within 2 Gb of RAM for a single core i586,<br>
something would have to go off an HD to make room for a full mercury<br>
build.<br>
<br>
I would propose adding advice for new users of mercury: plan to<br>
install on a recentlly defragged internal drive with 3 Gb free.<br>
Preferrrably run in parallel on multi-core CPU. If you got 'em, smoke<br>
em.<br>
<br>
Or some such.<br>
<br>
I would change the final build order of grade to do no-prof before<br>
with prof for fast-asm. Just a user suggestion: someone such as<br>
myself with a Prolog background is going to want a useable install<br>
against which to do some checks against the results <a href="http://m.org" target="_blank">m.org</a> and<br>
MissionCriticalIT indicate. What I had at 3am after several attempts<br>
is not yet that.<br>
<br>
Years of a low rate of user adoption could lead to neglect of<br>
user-adoption impediments: but for my interest, I would have abandoned<br>
the effort. Not providing optional binaries is one such ( I spent<br>
years in Smalltalk on large corp (F100, F200) mission critical apps -<br>
yet as a dev community we mastered the clean shot thru the foot.)<br>
<br>
Even on the 16 Gb SSD chip for this linux netbook (as the XP CPU is<br>
occupied with Mercury mgnuc), there are no longer 3 Gb to be freed and<br>
a 32Gb chip must await a contract.<br>
<br>
These are just the facts of my life as a user: I report them in the<br>
hope that input from the environment is what is critical to<br>
evolutionary change ;-)<br>
<br>
No unpleasant or sarcastic tone is intended. I am told that<br>
tolerating my manner of expressing myself is a question of an acquired<br>
taste. Having come to enjoy steamed spinach - but not stewed pears -<br>
I can imagine this ...<br>
<br>
If instead the build were controlled by a near-logic language such as<br>
ICON (oh never mind - at my age I won't live to see configure/make go<br>
extinct ). What fails, fails. Why backtrack to "finish" a build with<br>
some optimal outcome?<br>
<br>
Or: why is mercury not yet building mercury?<br>
<br>
Best regards<br>
an exasperated new user<br>
PS: and Smalltalk begat Ruby (yet Self-inlining begat Google V8.<br>
Hmmm. Why am I not more easily amused?)<br>
--------------------------------------------------------------------------<br>
mercury-users mailing list<br>
Post messages to: <a href="mailto:mercury-users@csse.unimelb.edu.au" target="_blank">mercury-users@csse.unimelb.edu.au</a><br>
Administrative Queries: <a href="mailto:owner-mercury-users@csse.unimelb.edu.au" target="_blank">owner-mercury-users@csse.unimelb.edu.au</a><br>
Subscriptions: <a href="mailto:mercury-users-request@csse.unimelb.edu.au" target="_blank">mercury-users-request@csse.unimelb.edu.au</a><br>
--------------------------------------------------------------------------<br>
</blockquote></div><br></div>