[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: mkoctfile problems with Octave 3.4.0, OSX 10.6.7
From: |
Scott Wardle |
Subject: |
Re: mkoctfile problems with Octave 3.4.0, OSX 10.6.7 |
Date: |
Thu, 21 Apr 2011 12:11:00 -0700 |
Hello Julien,
Thanks for the latest build. However, when using mkoctfile with the --mex
option (which I invoke using the "mex" command),
I'm still getting these warning and these undefined symbols:
octave-3.4.0:7> mex bitparitycheck.c -o bit_parity_check.mex
ld: warning: in /Applications/Octave.app/Contents/Resources/bin/octave-3.4.0,
file was built for i386 which is not the architecture being linked (x86_64)
ld: warning: in
/Applications/Octave.app/Contents/Resources/lib/octave-3.4.0/liboctinterp.dylib,
file was built for i386 which is not the architecture being linked (x86_64)
ld: warning: in
/Applications/Octave.app/Contents/Resources/lib/octave-3.4.0/liboctave.dylib,
file was built for i386 which is not the architecture being linked (x86_64)
ld: warning: in
/Applications/Octave.app/Contents/Resources/lib/octave-3.4.0/libcruft.dylib,
file was built for i386 which is not the architecture being linked (x86_64)
ld: warning: in /Applications/Octave.app/Contents/Resources/lib/libfftw3.a,
missing required architecture x86_64 in file
ld: warning: in /Applications/Octave.app/Contents/Resources/lib/libfftw3f.a,
missing required architecture x86_64 in file
ld: warning: in
/Applications/Octave.app/Contents/Resources/lib/gcc/i686-apple-darwin9/4.2.1/libgfortranbegin.a,
file was built for unsupported file format which is not the architecture being
linked (x86_64)
ld: warning: in
/Applications/Octave.app/Contents/Resources/lib/gcc/i686-apple-darwin9/4.2.1/libgfortran.a,
file was built for unsupported file format which is not the architecture being
linked (x86_64)
ld: warning: in
/Applications/Octave.app/Contents/Resources/lib/gcc/i686-apple-darwin9/4.2.1/libgcc.a,
file was built for unsupported file format which is not the architecture being
linked (x86_64)
Undefined symbols:
"_mxGetM", referenced from:
_mexFunction in bitparitycheck.o
_mexFunction in bitparitycheck.o
"_mxGetN", referenced from:
_mexFunction in bitparitycheck.o
_mexFunction in bitparitycheck.o
"_mxIsComplex", referenced from:
_mexFunction in bitparitycheck.o
"_mexErrMsgTxt", referenced from:
_mexFunction in bitparitycheck.o
_mexFunction in bitparitycheck.o
_mexFunction in bitparitycheck.o
"_mxCreateDoubleMatrix", referenced from:
_mexFunction in bitparitycheck.o
"_mxGetPr", referenced from:
_mexFunction in bitparitycheck.o
_mexFunction in bitparitycheck.o
_mexFunction in bitparitycheck.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
octave-3.4.0:8>
Perhaps these undefined symbols are due to the wrong architecture (x86_64) as
opposed to i386?
thanks!!
Scott
On Apr 21, 2011, at 4:37 AM, Julien Salort wrote:
> Hello,
>
> I've built a new version today that should fix these problems.
> http://upload.grenoble.cnrs.fr/telechargement/eOVUbOnrWB/octave-3.4.0-i386.dmg
>
> In addition:
> - I used a gfortran compiler that should now be fully compatible with
> 10.5
> - I added Gnuplot-4.4.3 compiled by Pantxo Diribarne in the Extras
> folder
> - All the dependencies are compiled universal (ppc & i386) so I should
> be able to make a ppc version soon.
>
> Can you tell me how this new version behaves on your machine ?
>
> Thanks,
>
> --
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing on a mailing list?
>
> _______________________________________________
> Help-octave mailing list
> address@hidden
> https://mailman.cae.wisc.edu/listinfo/help-octave