----- Original Message -----
From: "Meng-Yuan Huang" <[EMAIL PROTECTED]>
.
.
Did you only try MinGW compiler for my program? Did you try Visual C++ 6.0
for it?
I'm sorry my program compiled by MinGW actually can run correctly.
The "ret 4" assembly instruction generated by MinGW doesn't make programs
generated by MinGW wrong,
but it make Visual C++ 6.0 wrong.
Aaah ... I missed that. I was using MinGW compiler with MinGW-built gsl-1.11
static library.
When I try to use VC7.0 with MinGW-built static library, your program won't
build for me because of unresolved symbols '_atanh', '_acosh' and '_log1p'.
(Did you strike the same ? I'm using gcc-3.4.5, so perhaps things are a
little different.)
To overcome that problem, I created a copy of MinGW's libmingwex.a named
libmingwex.lib - and linked to the newly created libmingwex.lib as well as
libgslcblas.lib and libgsl.lib. (Note that libgslcblas.lib and libgsl.lib
are copies of libgslcblas.a and libgsl.a.)
When I do that, your program builds fine - and also runs fine !!
So, unfortunately, I can't reproduce your problem.
So, shouldn't I develop my programs by Visual C++ 6.0 compiler and
libraries generated by MinGW?
It generally works fine. As you can see, when you build apps using Visual
Studio against MinGW-built libraries, there can be a need to link explicitly
to one or more of the standard MinGW libraries. (In my limited past
experiences, I've sometimes had to link to MinGW's libgcc, libg2c, and
libcoldname when building with Visual Studio.)
As for your particular problem, it may well be worth your while to post to
the MinGW list. Someone there might have a better idea about the particular
problem you've struck.
Do you think there's something to be gained from using Visual Studio to
build apps against MinGW-built libs ? Why not just use MinGW ? (For all I
know, there may well be valid reasons :-)
Cheers,
Rob
_______________________________________________
Bug-gsl mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gsl
