Re: nasty link problem with Gfortran and G++ (C++) ???

On 1/10/2025 5:01 PM, Thomas Koenig wrote:

Lynn McGuire <lynnmcguire5@gmail.com> schrieb:

On 1/10/2025 3:27 AM, Thomas Koenig wrote:

Lynn McGuire <lynnmcguire5@gmail.com> schrieb:
>

I cannot get a small code sample with or without a DLL to exhibit the
problem.  Like I said, I thought it was something related to size of my
DLL.  And this is the small DLL, only 3 MB.

>
Regarding DLLs, I'm out... I don't think I have ever done one.
>
Which toolchain are you using?  Msys/mingw64 is probably the
preferred one.  (Personally, I use cygwin for Windows stuff (with
the mingw64 cross compiler), but that is because I like the
UNIXy look and feel of cygwin.)
>
Did you look at the symbols that can be found in the respective
DLLs, do they match your expectations?  (I presume you follow
>
https://stackoverflow.com/questions/48021991/creating-dll-with-gfortran-on-windows
>
).

>
For compilers and IDE, I am using GCC 14.1 that is in Simply Fortran 3.38.
     https://simplyfortran.com/

 Hm, OK.   I'm not familiar with how Simply Fortran operates; they do
not cooperate with the gfortran team (but rather make money off the
work of volunteers). If you have questions regarding teir toolbox,
this is best addressed to them.
 

For Unix utilities on Windows, I use the old Thompson Toolkit from 1987
that had the grep written in assembly language for SPEED.  Finding code
in 5,000+ subroutines across 60+ subdirectories requires SPEED.
     http://www.tasoft.com/toolkit.html

 Do you have a working nm?  If not, debugging this will be pretty
much impossible.

Yes, I do.  I am looking at the results right now.  35,932 lines of stuff.  I have confirmed that I am not using stdcall which may be wrong, I am not sure yet.  The Watcom F77, C, and C++ compilers used stdcall so I am familiar with it.
Thanks,
Lynn