JimmyC57 has asked for the wisdom of the Perl Monks concerning the following question:

ok

I downloaded DBD-ODBC-1.17, unpacked it and ran Makefile.pl.

i received this error:

Useless use of private variable in void context at makefile.pl line 595.
You are using a Perl configured with threading enabled.
Please read the warnings in DBI about this.
You should also be aware that on non-Windows platforms ODBC drivers come in two forms, thread-safe and non-thread-safe drivers and you may need to make sure you are using the right one.
Press return to continue...

I'm sorry to be so needy... but i have no idea what that means!

suggestions please??? besides get a new job!

Thanks!! Jim

Replies are listed 'Best First'.
Re: More ODBC Install Issues
by Corion (Patriarch) on Oct 02, 2008 at 14:19 UTC

    What part of the text do you have problems with?

    You are using a Perl configured with threading enabled.

    This is a statement about your Perl interpreter. As likely you're on Windows, it's not uncommon to have a Perl with threading enabled. There is no further action required on your part.

    Please read the warnings in DBI about this.

    This is a request that you read the documentation of DBI about threads. The action to take on your part would be to read the documentation of DBI about threads.

    You should also be aware that on non-Windows platforms ODBC drivers come in two forms, thread-safe and non-thread-safe drivers and you may need to make sure you are using the right one.

    As you're likely on Windows, this part is of little concern to you.

    Press return to continue...

    This phrase prompts you to press the return key to continue.

    I'm not sure which part of these instructions is giving you problems.

      Sorry I forgot the rest of the message...
      here is what happens when you hit enter

      Checking if your kit is complete...

      Looks good

      *** You're using Microsoft Visual C++ compiler or similar but the LIB and INCLUDE environment variables are not both set.

      You need to run the VCVARS32.BAT batch file that was supplied with the compiler before you can use it.

      A copy of vcvars32.bat can typically be found in the following directories under your Visual Studio install directory:

      Visual C++ 6.0: vc98\bin Visual Studio .NET: vc7\bin

      Find it, run it, then retry this.

      If you think this error is not correct then just set the LIB and INCLUDE environment variables to some value to disable the check.

      # Looks like your test died before it could output anything.

        You need a C compiler to compile DBD::ODBC. You need to ensure the environment is set up to use the C compiler. You can either do this finding and running vcvars32.bat or better still is if you have installed MS VC then there is usually a start menu item to open a command prompt with the enironment already set up for you. Do this then run perl Makefile.PL again.
Re: More ODBC Install Issues
by mje (Curate) on Oct 02, 2008 at 14:53 UTC

    You have not "received this error" as yet.

    The warning Useless use of private variable in void context at makefile.pl line 595. is down to

    # Following generates # Useless use of private variable in void context at Makefile.PL # but is required $rv;

    in the Makefile.PL and you do not need to worry about it.

    You should read the warnings in DBI about running a thread enabled perl especially if you intend writing perl code that uses threads.

    If you are not on Windows you also need to be aware of the difference between thread-safe and non-thread-safe ODBC drivers because thread-unsafe drivers won't work with a perl using threads.

    All these warnings came out because your perl is built threaded and hence you could run perl code using threads. Things get complicated when you do that. If you do not intend to run any perl code using threads you can ignore this entirely.

    Press a key and it will continue to process a Makefile and you can build it.
Re: More ODBC Install Issues
by mje (Curate) on Oct 02, 2008 at 15:13 UTC
    BTW, why "More ODBC Install Issues"? What issues could you possibly have had before the point you've just got to? Perhaps I missed a node else where.

      yes
      it started with ODBC XP Install issues
      sorry i thought it would be better to start a new node...
      should i have just updated the old one??
      Jim