[m-rev.] for review: mention possible fix to missing .mih problem on Mac OS X

[Ian MacLarty]

On Mon, Sep 6, 2010 at 4:27 PM, Julien Fischer
<juliensf at csse.unimelb.edu.au> wrote:
>
> On Mon, 6 Sep 2010, Ian MacLarty wrote:
>
>> On Mon, Sep 6, 2010 at 4:07 PM, Julien Fischer
>> <juliensf at csse.unimelb.edu.au> wrote:
>>>
>>> On Mon, 6 Sep 2010, Ian MacLarty wrote:
>>>
>>>> For review by Julien.
>>>>
>>>> README.MacOS:
>>>>        Suggest removing fink from the PATH if, after installing Mercury,
>>>> the
>>>>        user gets errors about missing .mih files.
>>>>        I had this problem and removing fink from my PATH fixed it
>>>> (though
>>>> I
>>>>        don't know why).
>>>>
>>>> Index: README.MacOS
>>>> ===================================================================
>>>> RCS file: /home/mercury1/repository/mercury/README.MacOS,v
>>>> retrieving revision 1.15
>>>> diff -u -r1.15 README.MacOS
>>>> --- README.MacOS        13 Jul 2010 05:48:19 -0000      1.15
>>>> +++ README.MacOS        6 Sep 2010 05:15:23 -0000
>>>> @@ -44,6 +44,9 @@
>>>> Mercury can currently only be compiled by gcc on Mac OS X.  It cannot
>>>> currently
>>>> be compiled with llvm-gcc or clang.
>>>>
>>>> +If, after installing Mercury, you encounter errors about missing .mih
>>>> files,
>>>> +and you have fink installed, then try removing the fink components from
>>>> your
>>>> +PATH (these usually start with /sw) and reinstalling.
>>>
>>> Do you still have the broken installation?  Are the .mih files present?
>>>
>>
>> After removing fink from my path and reinstalling I have a working
>> installation, with .mih files.
>
> I'm not asking about what happens when you reinstall.  I'm asking about
> the installation that originally had the problem.  Are the .mih files
> present in it?
>

No.

>>> I think the problem is that fink is overriding one (some?) of the
>>> system tools and the .mih files are not actually being installed in the
>>> first place.  If that's the case then, the right thing to do is actually
>>> remove fink from the PATH *before* installing Mercury.
>>>
>>> (If you still have the broken installation, does it work if you remove
>>> fink from the PATH?)
>>
>> I don't understand what you mean.
>
> Does the "broken" installation with the missing .mih files work if
> your remove fink from your PATH or is it still broken when you do that?
>

Well I haven't tested that exactly, but the installation contains no
.mih files, so I don't see that changing the path after installation
can help.

> I want to know whether if having fink your PATH when installing
> results in a broken installation and (2) whether such an installtion
> can be "fixed" simply by removing fink from your PATH or do you have
> to do a complete reinstall without fink in your PATH?
>

A complete reinstall is required (which is what I said in the README).

Ian.

--------------------------------------------------------------------------
mercury-reviews mailing list
Post messages to:       mercury-reviews at csse.unimelb.edu.au
Administrative Queries: owner-mercury-reviews at csse.unimelb.edu.au
Subscriptions:          mercury-reviews-request at csse.unimelb.edu.au
--------------------------------------------------------------------------