[Luiz Fernando Morales]

Hello fellows

I've tried to install MTEX 4.3 in my Mac running Matlab 2015b and got the message:

>> startup_mtex
initialize MTEX 4.3.0  ....********************************************************************************
  MTEX binary check failed!
 
  The original error message was:
  Error using call_extern (line 158)
Error running external program:

 /Users/luizfgmorales/Documents/MATLAB/mtex-4.3.0/c/bin/maci64/odf2pf /private/tmp/odf2pf3464.txt 2>> /private/tmp/output_LuizsMacbookAirlocal_luizfgmorales.log
 
  Check the following options:
  * Compile the binaries yourself.
  * Ask the maintainer for help!


When I tried to install on the same computer running Matlab 2014a, I've got this:

startup_mtex
initialize MTEX 4.3.0  .Warning: Function isgraphics has the same name as a MATLAB builtin. We suggest you rename the
function to avoid a potential name conflict.
> In path at 109
  In addpath at 86
  In startup_mtex>addpath_recurse at 321
  In startup_mtex>setMTEXPath at 134
  In startup_mtex at 58
...********************************************************************************
  MTEX binary check failed!
 
  The original error message was:
  Error using call_extern (line 158)
Error running external program:

 /Users/luizfgmorales/Documents/MATLAB/mtex-4.3.0/c/bin/maci64/odf2pf /private/tmp/odf2pf4352.txt 2>> /private/tmp/output_LuizsMacbookAirlocal_luizfgmorales.log
 
  Check the following options:
  * Compile the binaries yourself.
  * Ask the maintainer for help!



Any thoughts? MTEX 4.2.1 runs well on matlab 2014a


Have a nice weekend


Luiz

[Ralf Hielscher]

Hi Luiz,

the issue of the warning: Function isgraphics has the same name as a MATLAB builtin. We suggest you rename the

function to avoid a potential name conflict. 

Has been fixed in MTEX-4.3.1

As for the other error I'm a bit puzzled as I didn't touch the binaries for years now. Could you post  the log files at

/private/tmp/output_LuizsMacbookAirlocal_luizfgmorales.log

Ralf.

[David Mainprice]

a) try making a new download of mtex, remove the current version, restart (reboot) your Mac, make new installation again.

b) are sure you have turned off the new ‚System Integrity Protection‚ (SIP) of Mac OS 10.11 El Capitan has been

disabled and this has been checked twice via the terminal window using "csrutil

status”.

c) Some times it works better if you place the mtex-4.3.0 (or any version mtex) folder in the MATLAB folder on some Macs

d) check version of Matlab using ver('MATLAB’) and send the result to Ralf as the ‘is graphics’ problem is related to version of MATLAB.

all the best David

--
If you want to reduce the number of emails you get through this forum login to https://groups.google.com/forum/?fromgroups=#!forum/mtexmail, click "My membership" and select "Don't send me email updates". You can still get emails on selected topics by staring them.
---
You received this message because you are subscribed to the Google Groups "MTEX" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mtexmail+u...@googlegroups.com.
Visit this group at https://groups.google.com/group/mtexmail.
For more options, visit https://groups.google.com/d/optout.

[zachs...@gmail.com]

disabling  SIP does not fix this problem I still for the following error:

Warning: Function isgraphics has the same name as a MATLAB builtin. We suggest you rename the function to avoid a potential name conflict.

Warning: Function isgraphics has the same name as a MATLAB builtin. We suggest you rename the function to avoid a potential name conflict.

Warning: Function isgraphics has the same name as a MATLAB builtin. We suggest you rename the function to avoid a potential name conflict.

> In path (line 109)

  In addpath (line 88)

  In startup (line 4)

  In matlabrc (line 227)

initialize MTEX 4.3.1  .Warning: Function isgraphics has the same name as a MATLAB builtin. We suggest you rename the function to avoid a potential name conflict.

> In path (line 109)

  In addpath (line 88)

  In startup_mtex>addpath_recurse (line 321)

  In startup_mtex>setMTEXPath (line 134)

  In startup_mtex (line 58)

  In startup (line 7)

  In matlabrc (line 227)

...Warning: Function isgraphics has the same name as a MATLAB builtin. We suggest you rename the function to avoid a potential name conflict.

> In path (line 109)

  In addpath (line 88)

  In check_installation>check_mex (line 118)

  In check_installation (line 21)

  In startup_mtex (line 74)

  In startup (line 7 

  MTEX 4.3.1 (show documentation)

  Import pole figure data

  Import EBSD data

  Import ODF data

 

  Uninstall MTEX

[David Mainprice]

The Warning: Function isgraphics has the same name as a MATLAB builtin.

Is just that a Warning, normally this should not stop MTEX from working, the Warning message depends on the version of Matlab you are using

It would be useful if you send a message with your version of MATLAB.

all the best David

[Ralf Hielscher]

This error occurs because you added the mtex path with all subdirectories to the Matlab search path. You are supposed to add only the top level directory and to run 

startup_mtex

I hope this helps,

Ralf.

[Jules Dake]

Hi Ralf,

I'm having (I think) the same problem as Luiz trying to install MTEX 4.3.2 with Matlab2015b on Mac (OS X 10.11.4).

I download the mtex-4.3.2.zip file, unzip it, add the top-level directory to my path and run 'startup_mtex'. Then I get basically the same error message as Luiz. (I've attached my error message below along with the contents of the .log file.)

I also looked at the suggestions in the post titled "problem with MTEX 4.3.1", and updated Java and Xquartz, compiled and installed FFTW3 and NFFT3, removed MTEX, restarted my computer a bunch and tried to reinstall, but to no avail. The error message remains, and when I try to run the import wizard it always fails.

I even tried compiling MTEX, but I get this error during the make:

gcc -c -O3 -Wall -fomit-frame-pointer -fstrict-aliasing -ffast-math -mfpmath=sse,387 -mieee-fp -m3dnow -mmmx -msse -msse2 -I/usr/local/include/ -I/usr/local/include/ -I../include -c odf2pf.c -o odf2pf.o
error: unknown FP unit 'sse,387'

Is there any new information on this problem? How should I go forward from here?

Thanks for any help,
Jules


-- The information from Matlab's Command Window --

>> addpath /Users/jules/Documents/MATLAB/mtex-4.3.2
>> startup_mtex
initialize MTEX 4.3.2  ..../bin/bash: line 1:   724 Trace/BPT trap: 5       /Users/jules/Documents/MATLAB/mtex-4.3.2/c/bin/maci64/odf2pf /private/tmp/odf2pf8390.txt 2>> /private/tmp/output_julessMacBookProfritzbox_jules.log
/Users/jules/Documents/MATLAB/mtex-4.3.2/c/bin/maci64/odf2pf /private/tmp/odf2pf8390.txt 2>> /private/tmp/output_julessMacBookProfritzbox_jules.log: Trace/breakpoint trap

********************************************************************************
  MTEX binary check failed!
 
  The original error message was:
  Error using call_extern (line 158)
Error running external program:

 /Users/jules/Documents/MATLAB/mtex-4.3.2/c/bin/maci64/odf2pf /private/tmp/odf2pf8390.txt 2>> /private/tmp/output_julessMacBookProfritzbox_jules.log

 
  Check the following options:
  * Compile the binaries yourself.
  * Ask the maintainer for help!

********************************************************************************
/bin/bash: line 1:   727 Trace/BPT trap: 5       /Users/jules/Documents/MATLAB/mtex-4.3.2/c/bin/maci64/odf2fc /private/tmp/odf2fc8565.txt 2>> /private/tmp/output_julessMacBookProfritzbox_jules.log
/Users/jules/Documents/MATLAB/mtex-4.3.2/c/bin/maci64/odf2fc /private/tmp/odf2fc8565.txt 2>> /private/tmp/output_julessMacBookProfritzbox_jules.log: Trace/breakpoint trap
 done!
 
  MTEX 4.3.2 (show documentation)

  Import pole figure data
  Import EBSD data
  Import ODF data
 
  Uninstall MTEX
 

-- And the contents of output_julessMacBookProfritzbox_jules.log --

dyld: Library not loaded: /opt/local/lib/libfftw3.3.dylib
  Referenced from: /Users/jules/Documents/MATLAB/mtex-4.3.2/c/bin/maci64/libnfft3.1.dylib
  Reason: image not found
dyld: Library not loaded: /opt/local/lib/libfftw3.3.dylib
  Referenced from: /Users/jules/Documents/MATLAB/mtex-4.3.2/c/bin/maci64/libnfft3.1.dylib
  Reason: image not found

[Luiz Fernando Morales]

Dear Jules,

Most important, did you deactivate the System Integrity Protection of the Mac OS? If not, this might be the cause. See the link below how to do that:

http://m.imore.com/el-capitan-system-integrity-protection-helps-keep-malware-away

It should work now, if not, try delete the curretn mtex, download again, put it inside the matlab folder under Documents in the Mac.

Best

Luiz

 

On Fri, 8 Jul 2016 09:40:59 -0700 (PDT)
Jules Dake <jule...@gmail.com> wrote:
> Hi Ralf,
>
> I'm having (I think) the same problem as Luiz trying to
>install MTEX 4.3.2
> with Matlab2015b on Mac (OS X 10.11.4).
>
> I download the mtex-4.3.2.zip file, unzip it, add the
>top-level directory
> to my path and run 'startup_mtex'. Then I get basically
>the same error
> message as Luiz. (I've attached my error message below
>along with the
> contents of the .log file.)
>
> I also looked at the suggestions in the post titled
>"problem with MTEX 4.3.1

> <https://groups.google.com/forum/#!searchin/mtexmail/java/mtexmail/zTy-O9kbRn0/GYOSBeknFgAJ>",

> and updated Java and Xquartz, compiled and installed
>FFTW3 and NFFT3,
> removed MTEX, restarted my computer a bunch and tried to
>reinstall, but to
> no avail. The error message remains, and when I try to
>run the import
> wizard it always fails.
>
> I even tried compiling MTEX, but I get this error during
>the make:
> gcc -c -O3 -Wall -fomit-frame-pointer -fstrict-aliasing
>-ffast-math
> -mfpmath=sse,387 -mieee-fp -m3dnow -mmmx -msse -msse2
>-I/usr/local/include/
> -I/usr/local/include/ -I../include -c odf2pf.c -o
>odf2pf.o
> error: unknown FP unit 'sse,387'
>
> Is there any new information on this problem? How should
>I go forward from
> here?
>
> Thanks for any help,
> Jules
>
>

> *-- The information from Matlab's Command Window* *--*

> *-- And the contents of
>output_julessMacBookProfritzbox_jules.log --*

>
> dyld: Library not loaded:
>/opt/local/lib/libfftw3.3.dylib
>  Referenced from:
> /Users/jules/Documents/MATLAB/mtex-4.3.2/c/bin/maci64/libnfft3.1.dylib
>  Reason: image not found
> dyld: Library not loaded:
>/opt/local/lib/libfftw3.3.dylib
>  Referenced from:
> /Users/jules/Documents/MATLAB/mtex-4.3.2/c/bin/maci64/libnfft3.1.dylib
>  Reason: image not found
>
>
> Am Montag, 11. April 2016 10:22:54 UTC+2 schrieb Ralf
>Hielscher:
>
>> This error occurs because you added the mtex path with
>>all subdirectories
>> to the Matlab search path. You are supposed to add only
>>the top level
>> directory and to run
>>
>> startup_mtex
>>
>> I hope this helps,
>>
>> Ralf.
>>
>> On Saturday, April 9, 2016 at 4:58:47 PM UTC+2,
>>zachs...@gmail.com

>>>> * Hello fellowsI've tried to install MTEX 4.3 in my Mac
>>>>running Matlab
>>>> 2015b and got the message:*

>>>>
>>>> >> startup_mtex
>>>> initialize MTEX 4.3.0  
>>>> ....********************************************************************************
>>>>   MTEX binary check failed!
>>>>  
>>>>   The original error message was:
>>>>   Error using call_extern (line 158)
>>>> Error running external program:
>>>>
>>>>  /Users/luizfgmorales/Documents/MATLAB/mtex-4.3.0/c/bin/maci64/odf2pf
>>>> /private/tmp/odf2pf3464.txt 2>>
>>>> /private/tmp/output_LuizsMacbookAirlocal_luizfgmorales.log
>>>>  
>>>>   Check the following options:
>>>>   * Compile the binaries yourself.
>>>>   * Ask the maintainer for help!
>>>>
>>>>
>>>>

>>>> *When I tried to install on the same computer running
>>>>Matlab 2014a, I've
>>>> got this:*

[Jules Dake]

Ah, disabling the System Integrity Protection (which still sounds sort of scary) did indeed solve my installation problems. Thanks for pointing me in the right direction! Now, if only I could figure out how to import my data... :)

[Luiz Fernando Morales]

What about import_wizard?

Best

Luiz


On Mon, 11 Jul 2016 05:35:25 -0700 (PDT)

>> >mtexmail+u...@googlegroups.com <javascript:>.

[Jules Dake]

Yeah, everything is working great now. I hadn't used MTEX since the upgrade to 4.X and had to get used to the new notation and the fact that EBSD data are now always spatially indexed.
Thanks again,
Jules