[m-users.] Bug Report Mercury-14.01.1 Shared Memories access

[Robert Buckley]

Hello,

Yes, I was attempting to compile <file_name.m>. Using <module_name> now and
am able to compile all my files and everything working well. Thank you.

Best regards,
Robert Buckley

On Tue, Jun 6, 2017 at 7:24 PM, Robert Buckley <rbuckley at ieee.org> wrote:

> Thank you Zoltan and Julien,
>
> I have recompiled all my files and note some improvement, but still
> there's one command that can't find limber_std.so. I will continue working
> on this and tell you what I learn about the problem and what fixes it (from
> my end).
>
> My compile string is more complex. It is:
>     mmc --link-object /usr/lib/x86_64-linux-gnu/libgmp.a -m -r -H
> <module_name>
>     include the -p option for profiling
>
> Ah, I think I see my problem with compiling. I have been trying to compile
> the <file_name.m> not the <module_name(no m)>.
> I'll get back to you. Thank you.
>
> Best regards,
> Robert Buckley
>
> On Tue, Jun 6, 2017 at 6:20 PM, Julien Fischer <jfischer at opturion.com>
> wrote:
>
>>
>> Hi Robert,
>>
>> On Tue, 6 Jun 2017, Robert Buckley wrote:
>>
>> Thank you for your response. The command used was:
>>>     $ ./test_primeFactors_gmp 1234567
>>> A listing for test_primeFactors_gmp.m appears below.
>>> I too suspect the needed grade is not installed. You
>>> can see from the list of 10 installed grades what's
>>> there, but the file was compiled two years ago on a
>>> different system and I don't know what grades it had.
>>>
>>
>> So you have the executable from two years ago?  Assuming so and that
>> it's dynamically linked you can either do:
>>
>>    1. ldd ./foo
>>
>>    2. string foo | grep grade
>>
>> In the first case, the directory path pointing to the Mercury libraries
>> should contain the grade; in the second you should see the name of a
>> symbol which includes the grade (something along the lines of
>> MR_grade_v19_hlc_gc_tags3_ubf).
>>
>> I tried to recompile but it told me that there was
>>> nothing to compile. Perhaps I can make a trivial change
>>> to the file and recompile.
>>>
>>
>> What is the command line you are using to invoke the compiler?
>> (My best guess would be that you are doing something like:
>>
>>     mmc --make foo.m
>>
>> in which case you simply need to omit the '.m' extension.)
>>
>> How does one know or find out what grade is used when compiling when no
>>> particular grade has been specified?
>>>
>>
>> Look in the file $INSTALL/lib/mercury/conf/Mercury.config
>> and search for MERCURY_DEFAULT_GRADE.
>>
>> Julien.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurylang.org/archives/users/attachments/20170606/0674cc1e/attachment.html>