in reply to Re^2: Building DBI, DBD::ODBC for 64 bit perl Win
in thread Building DBI, DBD::ODBC for 64 bit perl Win

LNK1181: cannot open input file 'bufferoverflowU.lib'

Do you not have that file ? I find it in my Platform SDK's Lib folder. It should be readily available but just /msg me if you want me to send a copy of it over.

I've got the 64-bit MinGW compiler, and it seems to be basically functional, but I haven't got round to thinking about the changes one would have to make to the perl source (makefile.mk mainly, I guess) in order to build perl with that compiler. If you get somewhere with that I would be interested to hear about it.

Cheers,
Rob
  • Comment on Re^3: Building DBI, DBD::ODBC for 64 bit perl Win

Replies are listed 'Best First'.
Re^4: Building DBI, DBD::ODBC for 64 bit perl Win
by wilsonch (Novice) on Apr 30, 2008 at 23:48 UTC
    Hi Rob,

    Thanks for offering to send the lib to me. I have solved that problem this way.

    Install Windows Server 2003 R2 Platform SDK from the following link http://www.microsoft.com/downloads/details.aspx?familyid=e15438ac-60be-41bd-aa14-7f1e0f19ca0d&displaylang=en

    Then copy the bufferoverflowU.lib to the Windows SDK for windows server 2008 and .NET framwork 3.5 lib folder.

    Everything works fine afterwards! But why that file is missing even after a reinstall is still beyond my understanding... I guess Micro$oft is the reason.

    Thanks again for all the help

    Issue Closed 2008-05-01

[reply]
      But why that file is missing even after a reinstall is still beyond my understanding

      It may well be that, whereas the 2003 version needs bufferoverflowU.lib, the 2008 version doesn't.

      Because ActiveState build with 2003 and because that compuiler needs bufferoverflowU.lib, bufferoverflowU.lib gets listed in $Config{libs} and $Config{perllibs}. Once listed there, it needs to be locatable (even if the compiler you're using, or the task at hand, doesn't need bufferoverflowU.lib).

      I didn't think of it when I posted yesterday, but an alternative fix for you may well have been to simply remove 'bufferoverflowU.lib' from the libs and perllibs listing in Config_heavy.pl.

      These are the sorts of things one has to look out for if one elects to use a compiler other than the one that was used to build perl in the first place :-)

      Cheers,
      Rob
[reply]
        or create a dummy bufferoverflowU.lib
[reply]

In Section Seekers of Perl Wisdom