On Wed, Mar 9, 2011 at 2:08 PM, Sisyphus <[email protected]> wrote: > Hi, > > On Windows Vista 64, the demo program: > > ##################################### > C:\_64\c>type try.c > #include <stdio.h> > #include <complex.h> > > int main(void) { > double _Complex rop, op, power; > > __real__ op = 3.0; > __imag__ op = 0.0; > > __real__ power = 2.0; > __imag__ power = 0.0; > > rop = cpow(op, power); > > printf("%f %f\n", creal(rop), cimag(rop)); > > return 0; > } > > ###################################### > > The result: > > ###################################### > C:\_64\c>gcc -o try.exe try.c > c:/_64/mingw_straw/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.4.4/../../../../x86_64-w64-mingw32/lib/libmingwex.a(lib64_libmingwex_a-cpow.o): > In function `cpow': > /W64_157253-src/build-crt/../mingw-w64-crt/complex/cpow.c:39: undefined > reference to `_imp__pow' > collect2: ld returned 1 exit status > > ###################################### > > The version of gcc: > > ###################################### > C:\_64\c>gcc -v > Using built-in specs. > Target: x86_64-w64-mingw32 > Configured with: > ../gcc44-svn/configure --host=x86_64-w64-mingw32 --target=x86_64-w64-mingw32 > --disable-multilib --enable-checking=release --prefix=//mingw64 > --with-sysroot=//mingw64 > --enable-languages=c,c++,fortran,objc,obj-c++ --with-gmp=//mingw64 > --with-mpfr=//mingw64 > --disable-nls --disable-win32-registry > Thread model: win32 > gcc version 4.4.4 20100306 (prerelease) [svn/rev.157253 - mingw-w64/oz] > (GCC) > > ##################################### > > Is there a "personal build" I should be trying instead of the one that I > have ? >
For the record, I tried my latest personal build and there were no errors. I used the i686-linux -> w64 cross compiler, I didn't try it natively on win64 itself, however I doubt that it would change anything. > I know that the 4.6.0 cross-compiler that I have doesn't suffer from this > problem - its handling of the _Complex data types and functions is > excellent.). > I currently have: > ##################################### > C:\_64\c>x86_64-w64-mingw32-gcc -v > Using built-in specs. > COLLECT_GCC=x86_64-w64-mingw32-gcc > COLLECT_LTO_WRAPPER=c:/_64/mingw64/bin/../libexec/gcc/x86_64-w64-mingw32/4.6.0/l > to-wrapper.exe > Target: x86_64-w64-mingw32 > Configured with: > ../../../build/gcc/gcc/configure --target=x86_64-w64-mingw32 > --prefix=/c/bb/vista64-mingw32/mingw-x86-x86_64/build/build/root > --with-sysroot=/c/bb/vista64-mingw32/mingw-x86-x86_64/build/build/root > --with-gmp=/c/bb/vista64-mingw32/mingw-x86-x86_64/build/build/gmp/install > --with-mpfr=/c/bb/vista64-mingw32/mingw-x86-x86_64/build/build/mpfr/install > --with-mpc=/c/bb/vista64-mingw32/mingw-x86-x86_64/build/build/mpc/install > --enable-languages=all,obj-c++ > --enable-fully-dynamic-string --disable-multilib > Thread model: win32 > gcc version 4.6.0 20100414 (experimental) (GCC) > > ##################################### > > Is there a later build of that compiler ? > > >From the "automated builds" section I just grabbed: > http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Automated%20Builds/mingw-w64-1.0-bin_i686-mingw_20110207.zip/download > > Is it 64-bit or 32-bit ? (In any case it's 4.5.3, not 4.6.x.) > > Cheers, > Rob -- O.S. ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
