Rarely seen portlint errors

[Conrad J. Sabatier]

While checking the ports tree for ports which need to have their
CPPFLAGS moved out of the CONFIGURE_ENV variable, I noticed a number
of errors from the perl interpreter re: the use of uninitialized
variables in portlint.

In every case, portlint still appears to run to normal completion and
produce normal diagnostics, but I thought you may be interested in
trying to eliminate the cause of these errors.

I've attached a list of the ports where these errors occurred along
with their respective error messages, as well as the bash script I was
running at the time.
  
Thank you.

-- 
Conrad J. Sabatier
conrads at cox.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: portlint-errs
Type: application/octet-stream
Size: 1830 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20110919/0a80f9e4/portlint-errs.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: find-ports-needing-cppflags-fix
Type: application/octet-stream
Size: 640 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20110919/0a80f9e4/find-ports-needing-cppflags-fix.obj