[prev in list] [next in list] [prev in thread] [next in thread] 

List:       net-snmp-bugs
Subject:    [ net-snmp-Bugs-1387981 ] not checking of perl version during
From:       "SourceForge.net" <noreply () sourceforge ! net>
Date:       2007-08-25 2:20:05
Message-ID: E1IOlFt-0001Ir-8R () sc8-sf-mysql1-b ! sourceforge ! net
[Download RAW message or body]

Bugs item #1387981, was opened at 2005-12-22 03:56
Message generated for change (Comment added) made by sf-robot
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=112694&aid=1387981&group_id=12694

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: configure
Group: None
>Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: Johannes Schmidt-Fischer (johannessf)
Assigned to: Nobody/Anonymous (nobody)
Summary: not checking of perl version during configure

Initial Comment:
When building net-snmp 5.2.x some files are built using
the perl binary found at the target machine. The path
to the perl binary seems to be evaluated by configure,
and this path is used in setting up the makefiles.

A problem arises from that when the perl binary found
is too old. I have a case where the perl binary found
has a version 4.x which is way too old to run some of
the perl scripts delivered with net-snmp. Running make
it stops when building mib2c.conf.5 (under man/) since
the perl script used for that doesn't work with perl 4
(it complains about "my $variable"). Restarting make
skips this file since it already exists and is newer
than the dependencies (the file is empty since it has
been created using '>' but this cannot be checked
though make).

Is it possible to evaluate not only the path to the
perl binary but to also check perl's version and to
complain if this version isn't suitable for building
net-snmp?

----------------------------------------------------------------------

>Comment By: SourceForge Robot (sf-robot)
Date: 2007-08-24 19:20

Message:
Logged In: YES 
user_id=1312539
Originator: NO

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 180 days (the time period specified by
the administrator of this Tracker).

----------------------------------------------------------------------

Comment By: Thomas Anders (tanders)
Date: 2006-08-28 16:34

Message:
Logged In: YES 
user_id=848638

Can you retry with CVS MAIN, please? We've added a few Perl
checks that may already catch this.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=112694&aid=1387981&group_id=12694

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Net-snmp-bugs mailing list
Net-snmp-bugs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-bugs
[prev in list] [next in list] [prev in thread] [next in thread]