Re: [Mingw-w64-public] 64bit (g)fortran JNI

2011-04-16 Thread Hans Horn
Jim, msvcrt.dll lives in C:\Windows\system32, which is in my PATH variable. Remember, the dll w/o the fortran stuff works, the one with doesn't. thx., H. On 4/16/2011 2:47 PM, Jim Michaels wrote: > I should mention that one of those functions relies on msvcrt > apparently, which is a microsoft

Re: [Mingw-w64-public] 64bit (g)fortran JNI

2011-04-16 Thread Jim Michaels
I should mention that one of those functions relies on msvcrt apparently, which is a microsoft runtime DLL. if it's not present in the PATH, the program probably will not run? C:\downloads\attachments_2011_04_16>grep msvcrt *dump.txt f_dump.txt: DLL Name: msvcrt.dll f_dump.txt:[1017](sec 6

Re: [Mingw-w64-public] 64bit (g)fortran JNI

2011-04-16 Thread Jim Michaels
I can see that the function lists are different by about 12 or so functions in different places, kind of scattered. more on the fortran side than on the other side. I also can't remember how important this is in a DLL (whether they are supposed to match exactly). C:\downloads\attachments_2011_0

Re: [Mingw-w64-public] MPFR 3.0.1: 3 tests fail

2011-04-16 Thread Sisyphus
- Original Message - From: "Ruben Van Boxem" > > Three tests of MPFR 3.0.1 fail on mingw-w64, (sezero's 4.5.2 x64 > build). The "make check" log is attached. > If your build is seen as a cross-compilation (which, I think, happens if you provide --build and --host arguments to configure

Re: [Mingw-w64-public] MPFR 3.0.1: 3 tests fail

2011-04-16 Thread Ozkan Sezer
On Sat, Apr 16, 2011 at 6:59 PM, Ruben Van Boxem wrote: > Hi, > > I'm reporting it here first, because I don't know (haven't looked) how > to fix it, or if there is already a fix upstream. > > Three tests of MPFR 3.0.1 fail on mingw-w64, (sezero's 4.5.2 x64 > build). The "make check" log is attach

[Mingw-w64-public] MPC 0.9 problem: dllimport attribute and undefined references

2011-04-16 Thread Ruben Van Boxem
Hi, In my non-stop (*cough*) attempts to get GCC built, I've stumbled on undefined references in the MPC build. When linking the final library together, I get undefined references to (I think) every function defined in the library. Accompanying this... mildly uncomfortable... issue, is a lot of th

[Mingw-w64-public] MPFR 3.0.1: 3 tests fail

2011-04-16 Thread Ruben Van Boxem
Hi, I'm reporting it here first, because I don't know (haven't looked) how to fix it, or if there is already a fix upstream. Three tests of MPFR 3.0.1 fail on mingw-w64, (sezero's 4.5.2 x64 build). The "make check" log is attached. Ruben test.log Description: Binary data --

Re: [Mingw-w64-public] libgcc_s*.dll and libstdc++*.dll, 32 and 64-bit targets conflict

2011-04-16 Thread JonY
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/16/2011 15:23, Jim Michaels wrote: > Could the compiler writes for personal builds and auto builds please redesign > the compilers so that the 64-bit compilers use different library names for > their > dll's than the 32-bit counterparts? you c

Re: [Mingw-w64-public] win64 target: processor?

2011-04-16 Thread Ruben Van Boxem
Op 16 apr. 2011 08:44 schreef "Jim Michaels" het volgende: > > what processors does "Targeting_win64" or the other 64-bit targets target? > > AMD64? > > or does it also work with Intel EM64T or whatever it was called (things are getting fuzzy)? The instruction set on both types of processorsb is

[Mingw-w64-public] libgcc_s*.dll and libstdc++*.dll, 32 and 64-bit targets conflict

2011-04-16 Thread Jim Michaels
Could the compiler writes for personal builds and auto builds please redesign the compilers so that the 64-bit compilers use different library names for their dll's than the 32-bit counterparts? you can't put them both into the same directory and have it work. one of the problems I am having,