Hi jianfeng,

The first three uninitialized warnings suggest to me that $Config{cc} is unset, which would mean that your perl is not fit for the purpose of building perl extensions, and should be discarded.
Oops ... it's actually $config->{cc}, not $Config{cc} that's uninitialized, and they could be different things ... I haven't checked.
What does the following one-liner report for you:

perl -V:cc
[download]

Also, we see, in the output you've provided:

Generating a dmake-style Makefile
[download]

Runing nmake on a Makefile that has been generated for dmake is never going to work.
You should run dmake instead.
Or, if you really want to use nmake you could try forcing the build to write a Makefile for nmake, which you do by starting with:

perl Makefie.PL MAKE=nmake
[download]

IMO opinion, the easiest approach for you is to use Strawberry Perl instead of ActivePerl.
I would recommend the latest available "Portable" edition - and then use the make utility (gmake) and C compiler (gcc) that have shipped with that Strawberry Perl zip and are ready to use.

DISCLAIMER: I have no idea whether GPIB will install on Strawberry Perl.
GPIB seems to have not been updated since 2002, and there's an 11-year-old bug report that has not yet received any attention.
Also, the cpan-testers matrix shows that it fails to build straight out of the box for all of the Windows cpan-testers that tried it out. (But that might simply mean that c:\pgpib.conf was not found)
Update: A closer look suggests that the immediate problem lies with other missing prerequisite items.

Cheers,
Rob