.dll gurus,
Latest response from Jan Dubois of ActiveState:
On Fri, 24 Aug 2007, Suresh Govindachar wrote:
Sisyphus suggested linking with C:/opt/perl/lib/CORE/perl58.lib
(which does have the symbols in it) in the command that creates
if_perl.o and/or in the command that builds
Earlier, I asked the dll gurus,
Latest response from Jan Dubois of ActiveState:
On Fri, 24 Aug 2007, Suresh Govindachar wrote:
Sisyphus suggested linking with C:/opt/perl/lib/CORE/perl58.lib
(which does have the symbols in it) in the command that creates
if_perl.o and/or in
Solved with help from Brian Dessent on the MinGW mailing list.
Add -lperl58 at the very end (location matters) of the last command.
--Suresh
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit
Suresh Govindachar wrote:
Solved with help from Brian Dessent on the MinGW mailing list.
Add -lperl58 at the very end (location matters) of the last command.
--Suresh
This is understandable by assuming that the linker processes each object file
or library once, in the order
Hello,
Attached below is the result of issuing the following command
(command has been written in multiple lines to make it easy to
read):
C:\home\suresh\develop\vim\vim7\src
c:\opt\mingw\bin\mingw32-make.exe -f Make_ming.mak
FEATURES=HUGE DEBUG=no GUI=yes
[Yongwei Wu drew attention to if_perl.c]
Make clean was not removing an earlier, bad if_perl.c. In the
output I reported, if_perl.c was size 0. I manually deleted
if_perl.c, and now get other errors. Before telling what the
errors were, here's more background info:
It is a
Tony suggested looking at other builds -- however,
I have been getting sources and building by own vim
for over a year. My hard-drive crashed; have a
new hard-drive. I am doing the exact same thing I
used to do -- expcept I now have the latest release
of ActiveState perl and
