Re: MXE Octave: "... has no symbols" warning under Mac OS X

[Michael Goffioul]

On Mon, Sep 23, 2013 at 4:51 PM, Anirudha Bose <address@hidden> wrote:

Hi everyone.

I have been successful in eliminating the need for Macports in MXE. I compiled gfortran from source following closely the Portfile maintained by MacPorts and then used the compiled libraries to build Octave. Below is the result of otool on bin/octave. I think is acceptable.

IIITs-iMac-7:mxe-octave-anirudha mac6-user1$ otool -L ./dist/Octave-3.7.5.app/Contents/Resources/bin/octave
./dist/Octave-3.7.5.app/Contents/Resources/bin/octave:

    @executable_path/../lib/octave/3.7.5/liboctinterp.1.dylib (compatibility version 2.0.0, current version 2.1.0)

    @executable_path/../lib/octave/3.7.5/liboctave.1.dylib (compatibility version 2.0.0, current version 2.1.0)
    @executable_path/../lib/libhdf5.7.dylib (compatibility version 8.0.0, current version 8.4.0)

    @executable_path/../lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.7)

    @executable_path/../lib/libfontconfig.1.dylib (compatibility version 9.0.0, current version 9.0.0)
    @executable_path/../lib/libfreetype.6.dylib (compatibility version 16.0.0, current version 16.0.0)

    @executable_path/../lib/libexpat.1.dylib (compatibility version 8.0.0, current version 8.0.0)

    @executable_path/../lib/libcholmod.so (compatibility version 0.0.0, current version 0.0.0)
    @executable_path/../lib/libumfpack.so (compatibility version 0.0.0, current version 0.0.0)
    @executable_path/../lib/libamd.so (compatibility version 0.0.0, current version 0.0.0)
    @executable_path/../lib/libcamd.so (compatibility version 0.0.0, current version 0.0.0)
    @executable_path/../lib/libcolamd.so (compatibility version 0.0.0, current version 0.0.0)
    @executable_path/../lib/libccolamd.so (compatibility version 0.0.0, current version 0.0.0)
    @executable_path/../lib/libcxsparse.so (compatibility version 0.0.0, current version 0.0.0)
    @executable_path/../lib/libqrupdate.1.dylib (compatibility version 2.0.0, current version 2.0.0)
    @executable_path/../lib/libfftw3_threads.3.dylib (compatibility version 7.0.0, current version 7.2.0)

    @executable_path/../lib/libfftw3.3.dylib (compatibility version 7.0.0, current version 7.2.0)

    @executable_path/../lib/libfftw3f_threads.3.dylib (compatibility version 7.0.0, current version 7.2.0)

    @executable_path/../lib/libfftw3f.3.dylib (compatibility version 7.0.0, current version 7.2.0)

    @executable_path/../lib/libreadline.6.2.dylib (compatibility version 6.0.0, current version 6.2.0)
    @executable_path/../lib/libncurses.5.dylib (compatibility version 5.0.0, current version 5.0.0)

    @executable_path/../lib/libpcre.1.dylib (compatibility version 2.0.0, current version 2.1.0)

    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)

    @executable_path/../lib/libgfortran.3.dylib (compatibility version 4.0.0, current version 4.0.0)
    @executable_path/../lib/libquadmath.0.dylib (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib (compatibility version 1.0.0, current version 380.6.0)

    /System/Library/Frameworks/JavaVM.framework/Versions/A/JavaVM (compatibility version 1.0.0, current version 1.0.0)

    @executable_path/../lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.17.0)

I would like to submit a patch to my repo for incorporating the above changes. Am I allowed to do that even if the coding period has ended? I want to continue working on this.

You're welcome to continue working on it, that was one of our goals for the GSoC students, to have them stay in the octave community after GSoC ends. However, GSoC coding period is finished now. So you should tag your repo, so that you can make a distinction between the work done as part of GSoC and the rest (this will be needed for you when submitting your code to Google).

Michael.