Re: strcat not found--MinGW

[John W. Eaton]

On  2-May-2011, Daryl Lee wrote:

| On 5/2/2011 12:23 PM, John W. Eaton wrote:
|  > On  2-May-2011, Daryl wrote:
|  >
|  > | Just in case there may have been something flaky about the installation, 
I
|  > | removed and reinstalled both Mingw and Octave.  On the Mingw install, I
|  > | installed all the compilers and the developer environment.  On the Octave
|  > | installer, I selected the "Forge" option, which I don't think I had done
|  > | before.  I'm still getting the same error.  I'm sure there is a problem
|  > | passing the Octave search path to a stand-alone program in my Mingw
|  > | environment.
|  >
|  > What does the copy of Octave you installed on MinGW tell you for the
|  > following commands
|  >
|  >    octave_config_info ("prefix")
|  >    octave_config_info ("fcnfiledir")
|  >    OCTAVE_HOME
|  >    OCTAVE_VERSION
|  > ?
| 
| octave.exe:2> octave_config_info("prefix")
| ans = C:\Octave\3.2.4_gcc-4.4.0
| octave.exe:3> octave_config_info("fcnfiledir")
| ans = C:\Octave\3.2.4_gcc-4.4.0\share\octave\3.2.4\m
| octave.exe:4> OCTAVE_HOME
| ans = C:\Octave\3.2.4_gcc-4.4.0
| octave.exe:5> OCTAVE_VERSION
| ans = 3.2.4
| 
|  >
|  > What do the same commands return if you add them to the .m file that
|  > you are executing from your standalone program?
| 
| The fcnfiledir line is reformatted for email line length...
| 
| $ ./test5
| prefix:     \usr\local\octmgw32_gcc-4.4.0-dw2\octave\3.2.4-4
| fcnfiledir: \usr\local\octmgw32_gcc-4.4.0-dw2\octave\3.2.4-4\share\
|               octave\3.2.4\m
| home:       /usr/local/octmgw32_gcc-4.4.0-dw2/octave/3.2.4-4
| version:    3.2.4

Is your copy of Octave installed in C:\Octave\3.2.4_gcc-4.4.0?

What happens if you set OCTAVE_HOME=C:\Octave\3.2.4_gcc-4.4.0 in your
environment before running your standalone program?

Octave has some code to allow the installation to be relocatable on
Windows systems (see the function w32_set_octave_home in
src/sysdep.cc).  This is apparently working correctly for Octave
itself, but not when you are using it as an embedded interpreter.  I
don't see why, as it looks to me like the initialization function that
ultimately calls w32_set_octave_home is called regardless of whether
Octave is executed as an embedded interpreter.

jwe