note
syphilis
Hi [jianfeng],
<br><br><strike>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.</strike><br>
Oops ... it's actually $config->{cc}, not $Config{cc} that's uninitialized, and they could be different things ... I haven't checked.
<br>What does the following one-liner report for you:
<c>
perl -V:cc
</c>
Also, we see, in the output you've provided:
<c>
Generating a dmake-style Makefile
</c>
Runing <c>nmake</c> on a Makefile that has been generated for dmake is never going to work.
<br>You should run <c>dmake</c> instead.
<br>Or, if you really want to use <c>nmake</c> you could try forcing the build to write a Makefile for <c>nmake</c>, which you do by starting with:
<c>
perl Makefie.PL MAKE=nmake
</c>
IMO opinion, the easiest approach for you is to use [https://strawberryperl.com/releases.html|Strawberry Perl] instead of ActivePerl.
<br>I would recommend [https://strawberryperl.com/download/5.32.1.1/strawberry-perl-5.32.1.1-64bit-portable.zip| 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.
<br><br><b>DISCLAIMER:</b> I have no idea whether GPIB will install on Strawberry Perl.
<br>GPIB seems to have not been updated since 2002, and there's [https://rt.cpan.org/Public/Bug/Display.html?id=62235|an 11-year-old bug report] that has not yet received any attention.
<br>Also, the [http://matrix.cpantesters.org/?dist=GPIB%200_30;os=mswin32;reports=1|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>c:\pgpib.conf</c> was not found)
<br>Update: A closer look suggests that the immediate problem lies with other missing prerequisite items.
<br><br>Cheers,<br>Rob
11137500
11137500