From: Richard Haney <rfhaney@ya...> - 2003-01-02 20:12:42
This question should be of general interest because its
answer could allow more flexible use of the current MinGW
libraries (presumably compiled with gcc 3.2): Is there a
way to reliably link gcc-2.95.2-compiled programs to the
current MinGW libraries? Under what circumstances will a
gcc 2.95.2-compiled program link (using, say, gcc 2.95.2)
compatibly to a current MinGW library?
When I tested a gcc-2.95.2-compiled program with a simple
'readline("string");' statement and linked it using gcc-
2.95.2 to libreadline.a from the current MinGW gdb
subpackage, the resulting executable printed "string" (which
I suppose must represent a prompt of some sort), and the
program continued to completion when I pressed [return].
This seems a bit more of a test than what the configure
script does for a symbolic computation package know as
However, when I compiled an example (test.c from
examples\mingw32\dirent in mingw32-980701-4.zip), the
example worked fine when compiled by MinGW gcc 3.2 and
linked by MinGW gcc 3.2 to the current 'libreadline.a'. But
when I compiled the example with MinGW gcc 2.95.2 and linked
it (using MinGW gcc 2.95.2) to the current libreadline.a,
the resulting executable produced a page fault (at a
location in the executable).
Is there some reliable trick or work-around I can use to get
gcc-2.95.2-compiled modules to link successfully (say, using
gcc 2.95.2) to the current MinGW libraries?
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
The ABI/API changed. You will need to rebuild all objects and libraries.
Richard Haney wrote:
> This question should be of general interest because its
> answer could allow more flexible use of the current MinGW
> libraries (presumably compiled with gcc 3.2): Is there a
> way to reliably link gcc-2.95.2-compiled programs to the
> current MinGW libraries? Under what circumstances will a
> gcc 2.95.2-compiled program link (using, say, gcc 2.95.2)
> compatibly to a current MinGW library?